[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
Hello Daniel,
I think this is a legitimate use case for disable-output-escaping.
So with translate() you don't need a recursive approach.
Regards,
Joerg
Daniel Fisher wrote:
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Re: [xsl] string replacement for HTML tags
Subject: Re: [xsl] string replacement for HTML tags From: Joerg Heinicke <joerg.heinicke@xxxxxx> Date: Thu, 25 Apr 2002 22:34:57 +0200 |
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
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] string replacement for HTML t, Daniel Fisher | Thread | Re: [xsl] string replacement for HT, Wendell Piez |
Re: [xsl] Complex XPath Help, Christopher R. Maden | Date | Re: [xsl] Extending xsltproc?, Daniel Veillard |
Month |