This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: translate function & hex data
- To: "'xsl-list at mulberrytech dot com'" <xsl-list at mulberrytech dot com>
- Subject: RE: translate function & hex data
- From: "Pawson, David" <DPawson at rnib dot org dot uk>
- Date: Tue, 29 Feb 2000 16:18:42 -0000
- Reply-To: xsl-list at mulberrytech dot com
David Carlisle, repeating my similar question some time back.
I'll add it to the faq .
Like the earlier questionner, I 'wanted' this for non
ASCII output.
If I remember, the follow up went something like,
put in a 'dummy' valid XML character, then post process
to change it to a 'disallowed' character.
Regards, DaveP
>> Something special about null character?
>yes it's not allowed in XML. But then neither is character 1
>(not checking for
>disallowed characters is a known feature of the IE parser, if I recall)
>
>the XML char production is:
>
><prod id="NT-Char"><lhs>Char</lhs>
><rhs>#x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD]
>| [#x10000-#x10FFFF]</rhs>
><com>any Unicode character, excluding the
>surrogate blocks, FFFE, and FFFF.</com> </prod>
>
>in otherwords nothing in the ascii control range except tab, line feed
>and newline.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list