I get the correct behaviour with Saxon 6.5.4 which is an XSLT 1.0
processor. Did something in XSLT 2.0 change that altered the behaviour
of XSLT w.r.t xml:space?
No, but why are you useing xx:node-set at all with xslt2? You don't need
to use an extension function to process variables in xslt2 (and there is
no node set type at all in xpath2).
Your original version is an infinite loop so ought produce an error in
any processor
<xsl:template match="/">
<xsl:apply-templates select="exsl-common:node-set($rtf)" />
</xsl:template>
xx:node-set always returns a node set containing a single / node.
so the template that matches is / which just applies templates back to
the same nod ad infinitum. you pretty much always want to do
xx:node-set(..)/* so as to apply templates to the top level element
rather than the / node.
David
________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--