Interesting.  I write it out neatly in the xsl.  I don't normally look
at the fo.  I run embedded code where I normally run a transform with an
output result created from the FOP handler so I get out a document and
any fo generated would stay within the transformer.  If I run that same
transform with an empty byte stream result it gets the fo, so I have
done that a few times and saved the fo code to files which I never look
at unless there's an error to debug.  I see that fo does combine the
attributes.  Of course writing code in fo wouldn't make much sense since
it has the xml input in it unless you're printing a document where
nothing changes.

-----Original Message-----
From: Andreas Delmelle [] 
Sent: Friday, January 07, 2011 4:28 PM
Subject: Re: DO NOT REPLY [Bug 49186] Empty fo:inline objects with id
attribute generate blank line

On 07 Jan 2011, at 20:13, Eric Douglas wrote:


> <snip />
> A lot of people put xsl tags in line as you've done there with 
> white-space-treatment, but I think it's easier to read if you split 
> them out to their own tags.

Actually, I was just writing plain FO (= what results after applying the



Reply via email to