2006/8/10, Remo Liechti:
There it is.
Ok, this is an unrelated problem. After the block containing the "SPOC7: Prototype Description" text there is another fo:block with break-after="page", which creates a new page; which is empty, as there is no more text in the fo:flow. I guess that more complex DocBook documents may contain some information which will appear on the following pages. Hence the break-after. In your case, you'll have to customize the XSLT template generating this part of the output and remove the last fo:block break-after="page". Note also that there are elements in the fox: namespace in your generated fo file. Those correspond to extensions for the ancient 0.20.5 version of Fop. They aren't processed by Fop 0.92. If you use the latest DocBook stylesheets there are two parameters to enable Fop extensions: one for the 0.20.5 version and one for the latest one. You should disable the former and enable the latter (IIRC it is called "fop1.extensions"). (Note for Fop-dev regarding the break-after problem: That said, I think there's a bug as a new page is created while there is nothing more but whitespace characters in the flow. If I remove the indenting so that all the remaining </fo:block> closing tags are sticked together (so there is really nothing after the breaking fo:block), a new page is still created. Is this a known issue? Is it related to the whitespace handling problem?) Vincent
Thanks, Remo -----Original Message----- From: Vincent Hennebert [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 10. August 2006 12:58 To: fop-users@xmlgraphics.apache.org Subject: Re: PDF generation Can you please post the whole generated fo? Thanks, Vincent 2006/8/10, Remo Liechti: > Well, I took a look at the generated FO: > > <fo:page-sequence > xmlns:axf="http://www.antennahouse.com/names/XSL/Extensions"; > hyphenate="true" master-reference="lot" language="en" format="i" > initial-page-number="auto" force-page-count="no-force" ... > > Like you seem the force-page-count is set in the page-sequence, like > Vincent told me. So the XSL transaction generated the right FO. > > It seems like FOP 0.92 does not care about this attribute in > page-sequence... > > Any other ideas? > > Remo > > > > > -----Original Message----- > From: Remo Liechti [mailto:[EMAIL PROTECTED] > Sent: Donnerstag, 10. August 2006 12:42 > To: fop-users@xmlgraphics.apache.org > Subject: RE: PDF generation > > Thanks Chris, Thanks Vincent > There was some misunderstanding on my side, sorry about that. I > understand clearly now :) > > Thanks, again, > > Remo > > > -----Original Message----- > From: Vincent Hennebert [mailto:[EMAIL PROTECTED] > Sent: Donnerstag, 10. August 2006 11:51 > To: fop-users@xmlgraphics.apache.org > Subject: Re: PDF generation > > 2006/8/10, Remo Liechti: > > It's me again. > > Well, to pass parameters to the XLS works fine, now. For example I can > > define the paper size etc. > > > > In the FAQ on > > > http://xmlgraphics.apache.org/fop/faq.html#blank-page-between-page-seque > > nces is written in chapter 3.2: > > > > If you don't want to have this blank page, use > > force-page-count="no-force". > > > > Well, the force-page-count parameter is not recognized by the XSL. And > I > > think it's a FOP parameter because it's in the FOP FAQ. (so this > problem > > is NOT a docbook related problem) > > Actually yes. The transformation chain is the following: > DocBook XML > | > | XSLT transformation > V > FO file > | > | FOP processing > V > PDF file > > The force-page-count is an FO property that should be set to "no-force" > in the FO file. But as this FO file is generated by the DocBook XSLT > stylesheets, this is those stylesheets' job to set the property to the > right value. > > By default they seem to set it to something other than "no-force". There > is perhaps an XSLT parameter which allow to change the way this property > is generated. If not, you'll have to change one XSLT template. On > docbook-apps they'll be able to tell you what to do. > > Note the difference between XSLT parameters, which allow to easily > customize an XSLT transformation and may be set on the command-line, and > FO properties, which constrain the behaviour of the FO processor and are > only found in the FO file. This isn't the same level. > > I hope you see the point. It's all a bit confusing at the beginning. > > Vincent
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
