Subject: Re: Re: Unwanted Output Escaping
From: "gary cor" <stuff4gary@xxxxxxxxxxx>
Date: Thu, 23 May 2002 12:01:33 +0000
|
Oleg,
Sadly this is not a solution to our problem, the mark-up in the CDATA block
is most likely invalid mark-up that we don't control, hence we need to leave
it "as-is" through into our final output.
G.
From: Oleg Tkachenko <olegt@xxxxxxxxxxxxx>
Reply-To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: Unwanted Output Escaping
Date: Thu, 23 May 2002 14:38:28 +0200
gary cor wrote:
Attempting to pass XSL statements, including CDATA blocks as a parameter
to another template, eg:
<...>
<xsl:call-template name="container1">
<xsl:with-param name="content">
<xsl:call-template name="bob"/>
</xsl:with-param>
</xsl:call-template>
</...>
<xsl:template name="container1">
<xsl:param name="content"/>
<xsl:for-each select="msxml:nodeset($content)">
<xsl:copy-of select="."/>
</xsl:for-each>
</xsl:template>
<xsl:template name="bob">
<![CDATA[
<p>Hello</p>
]]>
Well, by this you said explicitly "that is character data, not markup right
here".
</xsl:template>
Unfortunately the output appears escaped as <Hello> , when no
escaping is needed.
And now you mean you want that character data to be a markup?
If so, why did you marked it as character data in xsl?
--
Oleg Tkachenko
Multiconn International, Israel
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
_________________________________________________________________
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
Cart
