<xsl:text disable-output-escaping="yes">&</xsl:text> produces "&"
so it's no surprise (and very consistent) that
<xsl:text disable-output-escaping="yes">&#64;</xsl:text>
actually produces "&#64;"
That means that disable-output-escaping is not being used at all. Are
you sure you are linerising from the XSLT system. If you use msxsl to
generate a DOM tree and linearise from the DOM then the linearisation
hints such as disable-output-escaping, and any attributes to xsl:output
have no effect. If d-o-e was being used above you would get
& and @ in the above two cases.
I will try with other xsl processors but I don't really expect any
difference in behavior.
You will see a difference in any system that supports d-o-e (which
includes msxsl in some configurations) and most other systems
saxon, xalan, etc.
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>
--~--