Re: [boost] [quickbook] Controling the layout of table columns in docbook/fo output

Subject: Re: [boost] [quickbook] Controling the layout of table columns in docbook/fo output
From: Daniel James (dnljms_at_[hidden])
Date: 2012-03-18 09:09:25

On 12 March 2012 20:20, Andreas Pokorny <andreas.pokorny_at_[hidden]> wrote:
> Hi,
> In an earlier thread I mentioned that I am using quickbook to write
> software design specification/documentation. The whole document grows
> nicely now. Since more people are contributing, I added howto chapters
> to the end of the document, including some kind of guided quickbook
> skeleton for new chapters and the quickbook documentation itself. The
> quickbook documentation creates warnings with fop:
> Mar 12, 2012 8:11:46 PM org.apache.fop.events.LoggingEventListener processEvent
> WARNING: table-layout="fixed" and column-width unspecified => falling
> back to proportional-column-width(1) (See position 1686:869)
> Mar 12, 2012 8:11:46 PM org.apache.fop.events.LoggingEventListener processEvent
> WARNING: table-layout="fixed" and column-width unspecified => falling
> back to proportional-column-width(1) (See position 1686:905)
> Mar 12, 2012 8:11:46 PM org.apache.fop.events.LoggingEventListener processEvent
> WARNING: table-layout="fixed" and column-width unspecified => falling
> back to proportional-column-width(1) (See position 1896:796)
>
> and more. That happens for every table. Inside the documentation about
> tables there one containing hello world source. There the proportional
> column width makes the source code leave the table and text area of
> the page.
>
> Is there a yet undocumented way to control column sizes?

No, if you want greater control over tables you need to write them in
docbook, which can be embedded in quickbook:

http://www.boost.org/doc/libs/1_49_0/doc/html/quickbook/syntax/phrase.html#quickbook.syntax.phrase.escape

If you can suggest changes to the generated table that avoids this
warning, it might be possible to improve the output, but we don't use
fop nowadays (the pdfs are generated using xep) so supporting it isn't
a priority.