On Feb 14, 2007, at 01:03, Daniel Noll wrote:
<snip />
(We do our own breaking by substituting <fo:block/> elements into
the appropriate places before running through FOP, although it
sounds like this attribute to make linebreaks significant may be
cleaner.)
FWIW: I've always considered the insertion of empty blocks more like
a FO-hack, a way to trick the processor. Very useful trick, in some
cases though. I've seen especially creative use of it in combination
with conditional negative space-before or space-after (a Norman Walsh/
Docbook idea, IIRC)
OTOH, if you /can/ do without them --i.e. there are no properties
specified on the block, so it's only used to emulate HTML's <br />--
then it's always better not to use them. Reason is that the Java
object corresponding to a fo:block is fairly large, even for empty
blocks. The less of them, the better for the memory footprint.
On top of that, the XSL transform should become much, much simpler,
as it becomes only a matter of adding an attribute.
Cheers,
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
