Hi Wendell,
What interests me about David's idea is not the solution to the marking-up
of strings problem, so much as the recursive "operate on a node set result
of an operation" tactic -- one that I think we will be seeing lots more of
since it will be implicitly licensed by XSLT 2.0's elevation of node-set()
from an extension function (which for whatever reason people are reluctant
to use) to a mandated feature of the language.
Yes, this is one of the nice features of XSLT 2.0 -- no RTFs any more.
However, David is not converting an RTF to a node-set here. He is converting
a string to a text node, so that he can use xsl:apply-templates on it.
It seems to me that even in XSLT 2.0 one would need to convert a string to a
text node in order to be able to apply templates on it.
Probably Jeni and Mike could explain?
It is the first step on the road to FXSL, isn't it? ;->
:o)
In fact, when adapting FXSL to run with XSLT 2.0, 99% of the work was to get
rid of all occurencies of the xxx:node-set() function.
=====
Cheers,
Dimitre Novatchev.
http://fxsl.sourceforge.net/ -- the home of FXSL
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list