OK. I have some sort of progress.

I found an answer on mail-archive.com (*) which explains how the
keep-together on the fo:table block is unable to split the table over
several pages using keep-together.within-column=auto because the
surrounding fo:block has keep-together.within-column=always.

I've got my document to display properly by editing the xsl-fo.
This is, of course, a solution in the xsl-fo domain, and I want to get a
fix at the DocBook level.

I've used <?dbfo keep-together="auto" ?> within my DocBook <table> to
get the innermost of these set correctly, but I need the parent block to
somehow get the attribute changed.

Can I do this from the DocBook level ?  I don't want to need to patch
the fo to get the formatting to work.
Do I need to put another <?dbfo keep-together="auto" ?> to get the
parent fo:block's attribute fixed ?
If so, where should this be done ?
Is there something else I need to change ?



Appreciatively,
Richard.


(*) http://www.mail-archive.com/[EMAIL PROTECTED]/msg07904


> -----Original Message-----
> From: Kerry, Richard 
> Sent: 18 December 2007 11:16
> To: [email protected]
> Subject: RE: [docbook-apps] Fop unable to render tables ? 
> (without intervention ?)
> 
>  
> I've tried setting fop1.extensions but I don't think it does anything
> for me regarding tables.
> It generates a bookmark-tree and gives a region the name "blank-body".
> 
> One problem I'd had was that I'd missed the <colspec> elements within
> the <tgroup>.  Having added those I'm no longer getting the many
> warnings about table-layout.
> 
> However, I am still gettting Fop attempting to place each table on one
> page only, and I get the warnings shown below for the two long tables.
> I did get these when I sent my earlier message on this subject but
> thought the other messages, with their many repetitions, were more
> important, so I neglected to include them in my posting.  I think
> actually these are the most significant in that they are telling me
> directly that it has placed the long tables on single pages.  There's
> nothing I can see in DocBook, or Chapter 30 of Rob Stayton's book, to
> indicate that I need to tell it to split a table over multiple pages -
> indeed I'd have thought it would default to doing so.  And I 
> can't find
> any attributes or anything that looks like it will enable splitting
> tables across pages.
> 
> 
> 
> These are the two warning messages that tell me directly that 
> there are
> tables on pages 3 and 6 that can't be fitted onto the single page.
> 
> 17-Dec-2007 13:34:20 org.apache.fop.layoutmgr.PageBreaker$1
> notifyOverflow
> WARNING: Content of the region-body on page 6 overflows the available
> area in block-progression dimension. (fo:page-sequence, location:
> 237/61)
> 17-Dec-2007 13:34:20 org.apache.fop.layoutmgr.PageBreaker$1
> notifyOverflow
> WARNING: Content of the region-body on page 3 overflows the available
> area in block-progression dimension. (fo:page-sequence, location:
> 237/61)
> 
> 
> Uncertainly,
> Richard.
> 
> 
> > -----Original Message-----
> > From: Andrew McFarland [mailto:[EMAIL PROTECTED] 
> > Sent: 17 December 2007 15:49
> > To: Kerry, Richard
> > Cc: [email protected]
> > Subject: Re: [docbook-apps] Fop unable to render tables ? 
> > (without intervention ?)
> > 
> > On 17/12/2007, Kerry, Richard <[EMAIL PROTECTED]> wrote:
> > 
> > <snip/>
> > > Fop is version 0.94, which I think is the latest.
> > <snip/>
> > 
> > Try setting fop1.extensions
> > 
> > http://docbook.sourceforge.net/release/xsl/current/doc/fo/fop1
> > .extensions.html
> > 
> > Also read chapter 30 of the Sagehill book,
> > http://www.sagehill.net/docbookxsl/Tables.html
> > 
> > And good luck. Tables drive me nuts :-)
> > 
> > Andrew
> > -- 
> > We can't change the past, but each of us, by challenging 
> prejudice and
> > intolerance, can help to change the future.
> > - Rabbi Jonathan Sacks, Address at Holocaust Memorial Day, 
> Westminster
> > Hall, London, 27th January 2005
> > 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: 
> [EMAIL PROTECTED]
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to