OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [docbook-apps] long text includes generating wasted page breaks

The FO processor bumps the start of the long example to the next page 
because of the keep-together.within-column="always" property on the block 
containing the example. That's from the 'formal.object.properties' 

You're wondering why, since it won't fit on the next page either, the FO 
processor doesn't just start it on page 1.  The way FO processors work with 
keeps is that the property adds a "keep condition" to the block, which is 
tested on the first page.  It fails to fit there, so it bumps it to the 
next page and consumes the keep condition.  On the second page there is no 
keep condition, so it just starts there.  The FO processor doesn't look 
ahead to see if it fits on the second page, and then backtrack to the first 
page.  It just processes the content for the current page.  For all it 
knows, the second page could be a bigger page-master that would fit the 
example, if it were to test it.  But it doesn't test it on the second page.

The solution is to add a processing instruction to this example:

<?dbfo keep-together="auto"?>

Now it should start on the first page.

Bob Stayton
Sagehill Enterprises
DocBook Consulting

----- Original Message ----- 
From: "Chris Chiasson" <chris@chiasson.name>
To: "Docbook Apps" <docbook-apps@lists.oasis-open.org>
Sent: Wednesday, October 18, 2006 4:34 PM
Subject: [docbook-apps] long text includes generating wasted page breaks

> Please have a look at the appendix A.1 of this file:
> http://chris.chiasson.name/temp/Engineering_Optimization/Engineering_Optimization.pdf
> It is generated by this short file:
> http://chris.chiasson.name/temp/Engineering_Optimization/HW1_Appendix.xml
> (please keep in mind that firefox does not show xmlns elements unless
> you hit view source)
> I don't know if the issue lies with the fo processor or with the
> generation of the fo, but I am guessing it just doesn't "see" that
> adding the pagebreak between the appendix title and the example title
> won't "help" (because the example will still break across pages).
> Very early in the process of creating this file (2 months ago?), it
> didn't have this problem. However, I don't know what is different now.
> What causes this phenomenon?
> -- 
> http://chris.chiasson.name/
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]