https://issues.apache.org/bugzilla/show_bug.cgi?id=49186
--- Comment #2 from Andreas L. Delmelle <[email protected]> 2011-01-07 12:18:10 EST --- Not immediately dismissing this, but it did get me wondering which situation is wrong. FOP does not generate an area for empty inlines if they have no id or markers that should be tracked, which is why there is a difference between the two cases. Now, if we have: <fo:block white-space-treatment="preserve"> <fo:block>There should be a blank line between this block</fo:block> <fo:block>and this block</fo:block> </fo:block> The output is rendered, as expected, with a line in between both blocks containing only a single space character. Same without white-space preservation, but only a zero-width space <fo:block> <fo:block>There should be a blank line between this block</fo:block> ​ <fo:block>and this block</fo:block> </fo:block> Checking http://www.w3.org/TR/xsl/#area-inline, it seems like even empty inlines are in fact supposed to generate an area (= content/allocation rectangle), regardless of whether an id or marker is present (?). If that is so, then /that/ would be the case that needs fixing, contrary to what the bug description indicates. The only way to really avoid that spurious blank space, would be to set the font-size of the empty inline to 0pt. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
