I read this (with the addition of the closing parenthesis) as replacing
less than greater than and ampersand with three unfamiliar character
entities.
Yes, except that character references are not entity references.
They are not just unfamiliar thay are the first three slots in the
"Private Use Area" ie permenantly unassigned unicode characters that will
never have unicode definitions but are left blank for uses within an
application.
The way I read the w3c spec, it looked like you'd have to enclose those
three output-character definitions in a named character map and make the
serializer aware of that map by specifying the name in the
use-character-map attribute of xsl:output. Did you assume that or am I
missing something?
That's correct sorry I didn't make that clearer.
Rather than using translate explictly, if I were doing thjis I'd define
a function xsl:my:d-o-e in some namespace that took a string and
replaced < > and & as I suggested so you could just do
<xsl:value-of select="my:d-o-e(.)"/>
where you needed to this.
David
________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--