> > Ive got a solution here that works first by sorting out the
> colspans,
> > then by processing the RTF produced from that vertically.
>
> On a conformant processor you'll need a node-set() extension
> function for that. (Are there some processors that don't flag
> this as an error?)
Saxon 7.8 :)
even if you say version="1.0"? Hmm If that's conforming to
xslt 2 spec I think there should be a change to the draft
spec to make it not conformant.
Note however that (just to be pedantic, for a change) that
isn't working by first making an RTF, as xslt2 doesn't have
result tree fragments (thank goodness:-)
I don't think that a 2.0 processor should enforce the node-set rule for
backwards compatibility. It should still honour the extension function
if its present in the 1.0 stylesheet, but not require it.
This will ease the transition from 1.0 to 2.0, allowing users to still
code in 1.0 but take advantage of the best bits of 2.0 (no node-set,
xhtml output etc).
andrew
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list