RE: Non-validating XSL processors

Subject: RE: Non-validating XSL processors
From: "Sebastian Rahtz" <sebastian.rahtz@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Sun, 24 Sep 2000 23:42:15 +0100 (BST)
Matthew Bentley writes:
 > >But the simple way to solve the problem (assuming that it's a real problem
 > >and not imagined) is to preprocess the source XML to replace the ampersands
 > >with something else, and then postprocess the output to put them back
 > again.
 > Thanks Mike - this is actually what I've been doing - I translate from '&'
 > to '$!$' - I was just wondering whether theres an alternative-
 > Matt


<!ENTITY foo "<Entity name='foo'>">

in the XML (ie redefine them) and then

<xsl:template match="Entity">
 <xsl:value-of  disable-output-escaping="yes" select="'&amp;"/>
 <xsl:value-of select="@name"/>
 <xsl:value-of  disable-output-escaping="yes" select=";"/>

in your XSL.

Dirty, isnt it.


 XSL-List info and archive:

Current Thread