Sigh. I was afraid that this would be the answer. My immediate reaction
is horror,
but maybe this wouldn't be too bad to implement. I don't have too many
templates
that will get matched inside the component processing.
since you are already using node-set it's probably simpler to do it in a
second pass, that only does this.
so
<xsl:variable name="x">
<xsl:apply-templates/><!-- whatever you were doing before -->
</xsl:variable>
<xsl:apply-templates mode="r" select="x:node-set($x)"/>
<xsl:template match="*" mode="r">
<xsl:copy>
<xsl:apply-templates seelct="@*|node()"/>
</xsl:copy>
</xsl:template>
<xsl:template match="@*" mode="r">
<xsl:attribute name="{name()}">
<xsl:value-of select="x:replace(...
<xsl:template match="text()" mode="r">
<xsl:value-of select="x:replace(...
________________________________________________________________________
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>
--~--