Thanks. So how does a Saxon 7 user accomplish what s/he was
doing with
saxon:output in Saxon 6 without a combinatorial explosion in
the number
of xsl:output variants?
If you have a use case that shows the need to set the attributes
dynamically, rather than just selecting one of a set of preconfigured
output formats, I suggest you submit it to
public-qt-comments(_at_)w3(_dot_)org(_dot_)
(The fact that one product offered the capability in an XSLT 1.0
processor won't cut much ice).
Michael Kay
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list