• To: <xml-dev@l...>
• Subject: Re: Detection of non-Unicode characters
• From: "Rick Jelliffe" <ricko@a...>
• Date: Tue, 27 Aug 2002 18:41:08 +1000
• References: <3D66A823.2060109@t...> <4DBDB4044ABED31183C000508BA0E97F040ABF38@f...> <3D66A823.2060109@t...> <4.3.2.7.2.20020826100147.00c101d0@m...> <009001c24d1d$3ea77f30$4bc8a8c0@A...>

 From: "Ann Navarro" <ann@w...>

> I just ran into this myself, with a styled apostrophe character -- which 
> was only reported as a problem by XML Spy 4.4 upon opening the 1.2MB XML 
> file (character was: Â (0xC2), ' (0x92)).

On thinking about this more, if you have one non-ASCII character ( a styled apostrophe)
and it being represented by two non-ASCII bytes, that is normally a sign that 
the file is actually encoded using UTF-8. 

Check if that entity has an encoding header saying "ISO-8859-1" by mistake,
and try removing it if it does (to force the use of UTF-8). 

Cheers
Rick Jelliffe

• References:
  • Re: Detection of non-Unicode characters
    • From: Tim Bray <tbray@t...>
  • Detection of non-Unicode characters
    • From: Mark Feblowitz <mfeblowitz@f...>
  • Re: Detection of non-Unicode characters
    • From: Ann Navarro <ann@w...>
  • Re: Detection of non-Unicode characters
    • From: "Rick Jelliffe" <ricko@a...>

• Prev by Date: IBM Spam?
• Next by Date: How to implement getElementById() with Xerces using XML Schema?
• Previous by thread: Re: Detection of non-Unicode characters
• Next by thread: Re: Detection of non-Unicode characters
• Index(es):
  • Date
  • Thread