I don't think I wrote that clearly--our current implementation in BLM: (1) in addAreas(), adds empty blocks to represent space-before & space-after in one method, and
(2) in getNextBreakPoss(), reduces the "stackSize" (BPD or "vertical" allowable writing area) to compensate for (1) above when generating subsequent text in another method. (2) sometimes happens without (1), resulting in the stackSize being reduced (i.e., fewer lines of text on the page) and an empty space occurring at the bottom. The implementation needs improvement, such that (1) and (2) either both occur or neither occur, depending on the "force" parameter you mention below. Also, just to make sure I understand clearly--when you say "force" I think you're referring to "conditionality" (retain/discard), not "precedence" (the latter of which does have a "force" value, but I don't think that what's intended here.) Here's the space-before & space-after definitions: http://www.w3.org/TR/2001/REC-xsl-20011015/slice7.html#space-before The (vague?) definitions of conditionality and precedence are here: http://www.w3.org/TR/2001/REC-xsl-20011015/slice4.html#spacecond Thanks, Glen --- "J.Pietschmann" <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > 2.) The space-after of a block ending at the > bottom of the page is not > > currently being added to the beginning of the > subsequent page. > > It shouldn't unless it is explicitely forced. > > J.Pietschmann > > __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree
