Hi, all Latest commits against PropertyManager, Block and Area begin to address boundary conditions on page and column breaks. What I mean by this is, in case nobody noticed, up til now if a block had a break-before="*page|column" on it, _and_ it was already leading in its context, the break would get forced nevertheless. The same goes for break-after. I have code in PropertyManager, relatively untested, which should address break-before boundary conditions. The equivalent needs to be done for break-after; this is a bit more complicated. Having a block with a break condition actually lead or trail in context, before imposing the break condition, is relatively rare, I think, so this may have not caused many problems. Leastways nobody has complained. Where it would cause issues is most likely in the case you are doing things properly, and using XSLT to generate your FO, and let's say that you use sections, and you put a break-before="page" on every section title; if a section leads off a page-sequence, which is pretty likely, then you would get an extra unwanted blank page. This should now be fixed. Regards, Arved Sandstrom -- Fairly Senior Software Type e-plicity (http://www.e-plicity.com) Halifax, Nova Scotia Wireless * B2B * J2EE * XML --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
