> -----Original Message----- > From: Clovis Wichoski [mailto:[EMAIL PROTECTED] > <snip /> > But with multiple pages like 500 pages the redesign must be in XML > source, that need redesign in all XSL too (HTML, PDF, TXT and many > others), this cause a rework that I attempted to avoid, and only needed > because FOP throubles with memory, this is only a relief. >
Hi, Can't you use multiple page-sequences instead of just creating one sequence 'interrupted' by the 'ctrlPage' template? A few remarks to help you on your way: 1. I can't seem to find the reason why you are placing the whole <fo:static-content > into a separate template, since it is ... well, static and it doesn't rely on the elements in the XML (unless something is missing). 2. In the ctrlPage template, you are testing for a position(): you could also use XPath to select these, like <xsl:apply-templates select="product[(position() mod 3) = 0] Then inside the product template, use <xsl:for-each select="preceding::product[position() < 3] /> to grab the two preceding product nodes. 3. Check our http://xml.apache.org/fop/resources.html page, among the books and articles, there's a link to Dave Pawson's XSLT FAQ. Over there, you'll find a lot of useful stuff (amongst others on grouping which I think you'll find particularly helpful), so I'll bet you can work out a redesign which affects only the XSL itself and leaves the other files alone. If you really can't get any further, try posting your problem on Mulberry's XSLT list. Warning: it's a quite high-traffic list, but the upside is that the tips are 'highly-usable' ;) Hope this helps! Cheers, Andreas
