This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Non-validating XSL processors
- To: xsl-list at mulberrytech dot com
- Subject: RE: Non-validating XSL processors
- From: "Sebastian Rahtz" <sebastian dot rahtz at computing-services dot oxford dot ac dot uk>
- Date: Sun, 24 Sep 2000 23:42:15 +0100 (BST)
- References: <A3BEF7539574D4119E61001083F94D780F30E1@WELBKSEMS02>
- Reply-To: xsl-list at mulberrytech dot com
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
put
<!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="'&"/>
<xsl:value-of select="@name"/>
<xsl:value-of disable-output-escaping="yes" select=";"/>
</xsl:template>
in your XSL.
Dirty, isnt it.
Sebastian
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list