• To: Matt Gushee <mgushee@h...>
• Subject: Re: Detection of non-Unicode characters
• From: "J.Pietschmann" <j3322ptm@y...>
• Date: Sat, 24 Aug 2002 20:18:30 +0200
• Cc: xml-dev@l...
• References: <4DBDB4044ABED31183C000508BA0E97F040ABF38@f...> <3D66A823.2060109@t...> <20020823223630.GA440@s...>
• User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020721

Matt Gushee wrote:
> The main problem I found was that the Word documents are full of
> characters like 0x07, 0x2012-0x2019, and the like.
...
> P.S. Why are those punctuation symbols illegal in XML, anyway?

They are not illegal AFAIK. What probably happens is that they
are usually encoded in UTF-16 in Word files and when copied
through the clipboard. If the application which puts the
characters into the target file is not smart about converting
them to the the encoding declared for the file, and perhaps
writing them as character references, the XML parser will have
trouble reading them. Parsers are not required to deal with
unannounced changes in the character encoding of their input.

J.Pietschmann

• References:
  • Detection of non-Unicode characters
    • From: Mark Feblowitz <mfeblowitz@f...>
  • Re: Detection of non-Unicode characters
    • From: Tim Bray <tbray@t...>
  • Re: Detection of non-Unicode characters
    • From: Matt Gushee <mgushee@h...>

• Prev by Date: RE: Re: Can XLink be fixed?
• Next by Date: Renamer-att (was: Can XLink be fixed?)
• Previous by thread: Re: Detection of non-Unicode characters
• Next by thread: Re: Detection of non-Unicode characters
• Index(es):
  • Date
  • Thread