Does anyone have the same problem and how
Quote:
to make the escape work? Thanks.
From the XSLT 1.0 Spec
http://www.w3.org/TR/xslt#disable-output-escaping :
"Since disabling output escaping may not work with all XSLT processors and
can result in XML that is not well-formed, it should be used only when there
is no alternative."
So an XSLT processor is not required to support d-o-e.
The real problem described in the original post is to *stop* using d-o-e.
Cheers,
Dimitre Novatchev.
"Jon" <Jon@discussions.microsoft.comwrote in message
news:B1B3FD9A-5D1C-4A7C-9A5A-60CF9D28B44B@microsoft.com...
Quote:
Hi,
>
I used XslCompiledTransform with the following Xsl file. The <xsl:text
disable-output-escaping="yes"does not work when using
XslCompiledTransform
to do the trnasform (namely the output contain < not <), while it works
when
using MSXML2 to do the transform. Does anyone have the same problem and
how
to make the escape work? Thanks.
>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" encoding="UTF-8"/>
<xsl:preserve-space elements="*"/>
<xsl:template match="/">
<port1 id="Common.Javascripts" version="$Revision: 8 $">
<port2>
<xsl:text disable-output-escaping="yes"><![CDATA[>
<object name="FileIO" classid="clsid:6F745082-4C31-4ADE-B83A-5B16C16BF86F"
codebase="scripts/bin/rwhelpers.dll#version=1,1,0,9"></object>
<script language="Javascript" src="scripts/ErrorHandler.js"</script>
]]></xsl:text>
</port2>
</port1>
</xsl:template>
</xsl:stylesheet>