Yes, the codepoint 0 is the only remaining obstacle that stops you handling
binary data as if it were a string.
Apparently it's difficult to support the ASCII NUL character because some
implementations are written in antiquated programming languages that don't
allow a NUL character in the middle of a string...
Michael Kay
http://www.saxonica.com/
-----Original Message-----
From: David Carlisle [mailto:davidc(_at_)nag(_dot_)co(_dot_)uk]
Sent: 02 June 2005 10:27
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: Re: [xsl] Ascii end-of-file character output in an XSL file
presumably in a system supporting XML 1.1 it will supprt an ad hoc
extension to xsd schema so that in fact you can use these
control codes
in XML so long as you use a numeric reference, presumably they will be
output as themselves in text output. Only null (ascii 0) can't be used
at all.
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>
--~--
--~------------------------------------------------------------------
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>
--~--