Except that RTF can be generated much more efficiently than
node-set; and some implementations fell into a trap somewhere
around this issue while implementing extension node-set call
-- making it too inefficient. Not having to explicitely
convert RTF to a node-set can lead to either inefficient code
or to complex non-local optimizations in the processor.
...are you saying keep RTF's (and the corresponding explicit node-set
conversion) in 2.0 for performance reasons?
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list