Re: [xsl] Removing namespaces without escaping CDATA???

["Mukul Gandhi" <gandhi.mukul@xxxxxxxxx>]

Thanks Abel for suggesting this solution. It looks good, and does what I wanted.

On 4/10/07, Abel Braaksma <abel.online@xxxxxxxxx> wrote:
> Hmm, not really an improvement, but when things "cannot be done" and
> when "things" cover a rather unusual request, I tend to try a rather
> unusual approach to solving it. If you want this, really, you don't need
> any d-o-e on elements, or implementation specific extension attributes.
> If you'd feel comfortable with using functions or call-template to
> achieve this goal, here's how, in plain portable XSLT 2.0 syntax (it is
> fairly straightforward):
>
> <xsl:output use-character-maps="cdata" />
>
> <xsl:character-map name="cdata">
>    <xsl:output-character character="&#xE0F1;" string="&lt;![CDATA["/>
>    <xsl:output-character character="&#xE0F2;" string="]]>"/>
>    <xsl:output-character character="&#xE0F3;" string="&lt;"/>
>    <xsl:output-character character="&#xE0F4;" string="&amp;"/>
> </xsl:character-map>
>
> <xsl:template match="/">
>    <xsl:copy-of select="f:make-cdata('my-cdata', 'less-then &lt; and
> ampersand: &amp;')" />
> </xsl:template>
>
> <xsl:function name="f:make-cdata">
>    <xsl:param name="elem-name" />
>    <xsl:param name="content" />
>    <xsl:element name="{$elem-name}">
>        <xsl:text>&#xE0F1;</xsl:text>
>        <xsl:sequence select="replace(replace($content, '&lt;',
> '&#xE0F3;'), '&amp;', '&#xE0F4;')" />
>        <xsl:text>&#xE0F2;</xsl:text>
>    </xsl:element>
> </xsl:function>
>
> <!-- output of the above -->
> <my-cdata><![CDATA[less-then < and ampersand: &]]></my-cdata>
>
>
> Not that I consider this good coding, but it offers a solution to your
> request (having control on which elements receive 'CDATA treatment'). I
> just want to show you that you can get it any way you'd like with the
> current possibilities of XSLT/XPath 2.0. Use xsl:output if the elements
> are static, use xsl:result-document if they are dynamic, use the above
> approach if you want full control.
>
> I know, in your post you say you want to give some kind of xpath or
> similar that points to the elements that need be escaped. This is most
> easiest achieved with either a micro-pipeline (take your whole output
> and process it again using the above function, but only for the required
> elements) or an extra cycle.
>
> Cheers,
> -- Abel Braaksma
>   http://www.nuntia.nl
>
> PS: not that with xsl:result-document all attributes are AVTs, _except_
> use-character-maps (taking multiple qnames), which means that you have
> to choose your character mappings carefully to prevent collisions.


--
Regards,
Mukul Gandhi