This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Resolving Unescaped Entity Refs


> 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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]