[
Lists Home |
Date Index |
Thread Index
]
- From: Eric Bohlman <ebohlman@netcom.com>
- To: Lucio Piccoli <Lucio.Piccoli@one2one.co.uk>
- Date: Fri, 7 Jul 2000 04:36:14 -0700 (PDT)
On Fri, 7 Jul 2000, Lucio Piccoli wrote:
> thanks for your response Rick,
>
>
> > If you need to be able to pin down the specific encoding problem, some
> > extra info would be helpful:
> > - Can you tell us what the particular UTF-8 encoding error is?
>
> org.xml.sax.SAXParseException: Character conversion error: "Unconvertible
> UTF-8 character beginning with 0x96" (line number may be too low).
It appears they're sending out character codes in the 128-159 range, which
are defined only in the Windows CP-1252 charset; that one looks like an
en-dash. I suspect you'll also find codes in the range 0x91-94, which is
where Microsoft tools put typographically-balanced curly quotes. If
you're really unlikely, you'll find curly quotes being used as attribute
value delimiters, which isn't even well-formed XML. But it looks like
their documents are actually encoded in win-1252 rather than UTF-8.
***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************
|
