[
Lists Home |
Date Index |
Thread Index
]
m batsis wrote:
> What I had in mind is avoidance of redundancy in presentation
> information, in much the same way htm:div elements with 'class' or
> 'style' attributes are used instead of htm:font and htm:center.
Can you elaborate? XSLFO does not have a fo:font or fo:center,
there is only a fo:block. The only potentially redundant elements
are fo:list-block and related children (can be emulated with a table).
One issue could be that there is no equivalent of a 'class' attribute,
which indeed causes a lot of repeated sets of attributes on FO
elements. However, it seems this was intentional, you'll find the
equivalent of "class" in XSLT as use-attribute-sets. I wish
xsl:attribute-set and use-attribute-sets had been put in XSLFO
instead of XSLT.
> Thanks. Well, reading a friendly reply like yours, made me try and find
> arguments against myself. What came out of this is simply that XSL-FO
> presentation info can be transformed via XSLT, something that would be
> almost impossible by using CSS notation for that information...
As Ken already said, this also works the other way around, it is
easier in XSLT to override single attribute values than values
already buried in a "style" string, for example:
<fo:block font-size="12pt">
<xsl:if test="@importance='high'">
<xsl:attribute name="font-size">28pt</xsl:attribute>
<xsl:attribute name="font-weight">bold</xsl:attribute>
</xsl:if>
<xsl:apply-teplates/>
</fo:block>
I don't think I'd even try to do something similar if all
properties were in a single string.
J.Pietschmann
|
