Clay Leeds wrote:
I was unaware of the "waste of resources" issue. This might be useful
information to add somewhere (Run Page? FAQ?), when users are trying to
improve the performance of FOP.
I'm not sure the waste is significant enough to hamper performance.
It's just yet another object in the FO tree. If you use *lots* of
inline, and memory is already tight (as I heve seen in case of big
tables), well, then ....
If FOP were properly implemented, i.e. if fo:inline would generate
an area as it should (several bugs in bugzilla for this), then
ressource waste would be more severe. However, currently fo:inline
is exactly the same as fo:wrapper.
(BTW this means get used to fo:wrapper for changing font size and
doing text decorations, because fo:inline generates area objects in
HEAD).
I use fo:inline frequently in my XSL-FO templates to place a smaller
"space" between label text inherited font-size="10pt":
<fo:block font-size="10pt">
First<fo:inline font-size="4pt"> </fo:inline>Name
</fo:block>
Would it be more efficient (or more "proper") to use fo:leader instead?
More efficient? No, leaders create even an object more and
take more processing power.
More proper? It depends. The width of a non-breaking space
is not necessarily the font size, therefore you might have
to experiment in order to get the space width you want. A
leader will generate the correct space without such fiddling.
OTOH, you can't underline a leader, so ther's still a use case.
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
