> I may be misunderstanding your question, but it seems like you just need > one fo:page-sequence, with predefined fo:static-contents for the header > and footer (fo:static-contents will get automatically printed on each > page.) Next, put all the content that will be placed on each page in > the one fo:flow for the fo:page-sequence.
He is probably using the multiple page sequences to work around the memory issues in tables. I would say that most all of us who use 20.5 do this. I've written lots of xsl:fo that does its own page sequencing by counting lines of data, and we tend to design our reports differently to overcome the limitations in fop. I've seen mention of memory fixes on this list, but most of us are hesitant to do our own pulls from CVS. If the developers don't feel like this code is worthy or stable enough for a release of any kind, then we are not putting it into production. However, if you were to take the latest source and put it into a 20.5.1, we'd probably enthusiastically take it, and it might solve a lot of the performance/memory issues that are posted to the list. Dave -----Original Message----- From: Glen Mazza [mailto:[EMAIL PROTECTED] Sent: Monday, December 05, 2005 4:42 PM To: fop-users@xmlgraphics.apache.org Subject: Re: Page Sequences Clifton Craig wrote: > I'm writing a report transform usinf XSLT for XSL-FO and I have some basic > questions. What's the best way to code for multiple page sequences. For > example I have some static content that I like to keep in the header and > footers and I guess it doesn't matter but I'd like to reuse chunks of XML-FO > for that purpose rather than replicating it to the result tree. I may be misunderstanding your question, but it seems like you just need one fo:page-sequence, with predefined fo:static-contents for the header and footer (fo:static-contents will get automatically printed on each page.) Next, put all the content that will be placed on each page in the one fo:flow for the fo:page-sequence. > > Now from within that template I want to start new page sequences and spit out > the following using a new-page XSLT-template: > The page handling is done by FOP -- you won't know the number of pages needed, that is done by FOP's layout process. > > What bothers me even more is since I'm > programmatically controlling new pages is there a better way to handle this > type of processing? Right now it looks like I'll have to keep a line count in > my stylesheet to detect when I should programmatically start new pages. Is > there a better way? How do most people do multipage reports with variable > data? Iss everybody line counting in there stylesheets? I don't think anybody does that. Place all your content (except for the header and footer) in the single fo:flow of the fo:page-sequence, and that should work. Glen --------------------------------------------------------------------- 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]
