• To: xml-dev@l...
• Subject: Re: baffling encoding problem
• From: richard@i... (Richard Tobin)
• Date: Wed, 9 Feb 2005 12:56:28 +0000 (GMT)
• Cc:
• In-reply-to: <1107953143.420a05f800548@h...>
• Organization: HCRC, University of Edinburgh

In article <1107953143.420a05f800548@h...> you write:
>The instance has a declared encoding of UTF-8 and a BOM
>of UTF-8 (EF BB BF).
[...]
>When I open it in 010 editor, the hex editor i use, it shows 42F8 726E
>6568 6176 6 which that's right isn't it? I copy that I get Børnehave. 

That "F8" is the Latin-1 code for o-with-stroke.  So it appears that your
document is not in UTF-8 but in Latin-1.  Change the encoding declaration
to "iso-8859-1".

The applications that show it correctly are doing so because they are
ignoring the declared encoding, and assuming that it's Latin-1 (or
some proprietary Windows character set vaguely related to Latin-1).

-- Richard

• References:
  • baffling encoding problem
    • From: Bryan Rasmussen <bry@i...>

• Prev by Date: baffling encoding problem
• Next by Date: RE: Re: Where does the "nothing left but toolkits" myth come from?
• Previous by thread: baffling encoding problem
• Next by thread: Re: baffling encoding problem
• Index(es):
  • Date
  • Thread