This is weird. The bug does not seem to be present in the latest FOP Trunk anymore, but I can't find any explicit fix for this bug. Would it be possible for you, Will, to recheck with the latest code from Subversion?
BTW, I had obviously processed the test case I got in December and added a test case (block_break-after_2.xml) to our test suite. And this test miraculously passes right now in FOP Trunk. Hmm. On 22.02.2006 23:16:53 Jeremias Maerki wrote: > It rings a bell. I already have a test case sent to me by Dominic > Brügger, which it seems I have managed to misplace. Sorry, guys! I've > only just found it again after searching my archive. I'll look into it > on Friday. > > In the meantime, the work-around is to replace break-after with > break-before (if that's possible). > > On 22.02.2006 22:30:59 Will Peterson wrote: > > I'm using the FOP 0.91beta. Whenever I use the break-after="page" in a > > block, any document after that point does NOT get rendered after that > > point. It inserts the page break and then the rest is gone. If I > > render to RTF, the page break is not a problem (but does not appear to > > be inserted) > > > > For example the following line would cause any XSL below it to be > > ignored. > > > > <fo:block xmlns:fo="http://www.w3.org/1999/XSL/Format"; > > break-after="page"/> > > > > Any ideas on what is going on here? > > > > Thanks. Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
