Subject: Re: [xsl] invalid character (Unicode: 0xa0) in xsl document - LONG From: Mike Brown <mike@xxxxxxxx> Date: Sun, 29 Apr 2001 01:31:04 -0600 (MDT) |
Joshua Allen wrote: > This is correct -- 0xA0 cannot appear as the first byte of a UTF-8 > sequence [1]. True. > This character could easily appear as the second byte of > a two-byte sequence, True. > and I could also see the error appearing IF you receive a UTF-8 file > that does not have a BOM, and is in a different byte-order than your > system expects False. BOMs and endianness are irrelevant in UTF-8. See http://www.unicode.org/unicode/faq/utf_bom.html#3 - Mike _____________________________________________________________________________ mike j. brown, software engineer at | xml/xslt: http://skew.org/xml/ webb.net in denver, colorado, USA | personal: http://hyperreal.org/~mike/ XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] invalid character (Unicod, Joshua Allen | Thread | Re: [xsl] invalid character (Unicod, Mike Brown |
[xsl] matching input value to a nod, tanz | Date | Re: [xsl] invalid character (Unicod, Mike Brown |
Month |