Re: Some reflections on using quickbook

Joel de Guzman wrote:
> Reece Dunn wrote:
> > Hi,
> >
> > I am getting used to the quickbook format (a lot faster to write and 
> > easier to read than boostbook!) However, I have a few observations:
> >
> > 1.  Tables - I can't specify row or column spans (cells that span 
> > several rows or columns). This is easy in HTML via rowspan and 
> > colspan, but there is no quickbook equivalent.
>
> Nor is there a DocBook equivalent, unless I am mistaken.

Oh well. This would have been nice to have.

> > 2.  Pre - the following fragment isn't processed correctly:
>
> Because "pre" is a block level markup. Use:
>
>  [^cat file.txt | grep -F hello]
>
> instead.

Thanks :)

> > 4.  Code - adjacent code fragments aren't concatenated:
> >
> > [For example:
> >   ``int foo()``
> >   ``{``
> >   ``}``
> > ]
>
> Shouldn't that be:
....
>   ``
>   int foo()
>   {
>   }
>   ``
....
> ??

But if there is whitespace before the code text (as indicated by the 
.... I added for illustrative purposes) then the whitespace is retained 
and if this is indented to contain a large number of spaces, the code 
doesn't look good. Also, doesn't your example add newlines above and 
below? What if I wanted to avoid that?

> > 5.  Code fragments spanning multiple lines retain all whitespace, thus 
> > the code fragment:
> >
> > [For example:
> >   ``int foo()
> >     {
> >        std::cout << "bar" << std::endl;
> >     }``
> > ]
> >
> > gets incorrectly formatted w.r.t. spacing.
>
> What were you expecting?

From the way it currently works, something like

int foo()
     {
        ...
     }

Ideally, I'd like it to see the opening `` and note the number of 
whitespace before it (adding two for the `` marker) then removing that 
much whitespace from each subequent line, giving:

int foo()
{
   ...
}

It's ok if this is not implemented as there are ways around it.

I've also noticed that:

[table
[[...] [...] [...]]
[[Minimize CRT Use in ATL] [Foo] [
ATL is not natively supported in BBv2, so this is the default.
``feature atl-minimum-crt : no yes : propagated composite ;
feature.compose <atl-minumum-crt>yes : <define>_ATL_MIN_CRT ;``
]]

[[Minimize CRT Use in ATL] [Bar] [
ATL is not natively supported in BBv2, so this is the default.

``feature atl-minimum-crt : no yes : propagated composite ;
feature.compose <atl-minumum-crt>yes : <define>_ATL_MIN_CRT ;``
]]
]

The table row containing "Foo" will compile cleanly, but "Bar" will 
generate syntax errors (note the additional line spacing).

- Reece



-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Boost-docs mailing list
Boost-docs@xxxxxxxxxxxxxxxxxxxxx
Unsubscribe and other administrative requests: 
https://lists.sourceforge.net/lists/listinfo/boost-docs