Lists Home |
Date Index |
David Carlisle wrote:
> same here, but I don't really see the advantage in css styling in that
> case. Except for those features that are only available in CSS
> rather than native html/svg. In the case of FO there are no such
> features as it's a superset of CSS rendering model (I think?).
Ok, the reason I think XSL-FO should use CSS in the same way as
SVG does is not because I want to use some specific styling properties
of CSS. The reason is that I think CSS is a better tool for associating
styling properties to nodes in a structure than XSLT is. The benefits come
from of a combination of the compact notation and the cascading rules.
> Why is it easier to generate class="foo" in the XSLT together with
> some css styling for .foo than to generate that set of attributes
> directly in the XSLT using an attribute set or variable containing a set
> of attribute nodes? I don't understand.
For the reasons I mention above I think it is much more efficient to manage
a set of largely static styling properties in CSS files rather than in
the XSLT files. Another reason is consistency with how I do very similar tasks
in HTML and SVG.