This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Resolving Unescaped Entity Refs
- From: "Nik Krimm" <Nik dot Krimm at emacdigital dot com>
- To: <XSL-List at lists dot mulberrytech dot com>
- Date: Tue, 30 Apr 2002 13:09:07 -0500
- Subject: [xsl] Resolving Unescaped Entity Refs
- Reply-to: xsl-list at lists dot mulberrytech dot com
> Hi all:
> I am working on a transformation that uses the same 4 letter 'code' as a back-end parameter and an entity reference. Currently the 'code' appears twice for each node - once escaped and once not escaped, and I'd like to find a way to eliminate one.
>
> Current Example:
>
> <node display="&code;">code</node>
>
> I'd like to replace it with:
>
> <node>code</node>
>
> and create functionality that would resolve this using an entity reference in an external DTD (<!ENTITY code "Resolved Display Value">)
>
> I thought I could use <xsl:value-of select="unparsed-entity-uri(/node) />, however, in testing I find this is incorrect.
>
> Any ideas? I'm using Xalan as a transformation engine.
>
> TIA
>
> nik
>
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list