This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: string replacement for HTML tags
- From: Joerg Heinicke <joerg dot heinicke at gmx dot de>
- To: xsl-list at lists dot mulberrytech dot com
- Date: Thu, 25 Apr 2002 22:34:57 +0200
- Subject: Re: [xsl] string replacement for HTML tags
- References: <200204251704.ABG42251@vivi.cc.vt.edu>
- Reply-to: xsl-list at lists dot mulberrytech dot com
Hello Daniel,
I think this is a legitimate use case for disable-output-escaping.
<xsl:template match="data">
<xsl:value-of disable-output-escaping="yes"
select="translate(., '[]', '<>')"/>
</xsl:template>
So with translate() you don't need a recursive approach.
Regards,
Joerg
Daniel Fisher wrote:
> Hello,
> I'm trying to do some string replacement in my transform to generate HTML.
> Basically I've got a node like this:
>
> <data>This text is [b]bold[/b]</data>
>
> When I've finished my transform I want:
>
> This text is <b>bold</b>
>
> This seems pretty easy using recursion, however it becomes a mess if you introduce
> multiple string replacements to support tags like [u] and [i].
>
> Is it possible to store the results from a template without displaying them
> and then perform several string replacements on the results?
>
> Once I've made all the replacements I need I could then display the final results.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list