Re: Unexpected conversion from AL32UTF8 to WE8ISO8859P1
From: Laurenz Albe <invite_at_spam.to.invalid>
Date: 14 Jan 2009 10:11:43 GMT
Message-ID: <1231927902.430307_at_proxy.dienste.wien.at>
Jaap W. van Dijk <j.w.vandijk.removethis_at_hetnet.nl> wrote:
> Thanks for diving into this! In an other posting in this thread I came
> to the same conclusion.
Date: 14 Jan 2009 10:11:43 GMT
Message-ID: <1231927902.430307_at_proxy.dienste.wien.at>
Jaap W. van Dijk <j.w.vandijk.removethis_at_hetnet.nl> wrote:
> Thanks for diving into this! In an other posting in this thread I came
> to the same conclusion.
I saw your posting only after I had written this :^/
> How did you come by your information on valid UTF-8 codes?
I got an error message from "iconv", but here is the official way:
Read RFC 2279 and look at the possible octet sequences in chapter 2.
A two-byte UTF-8 sequence looks like this:
110xxxxx 10xxxxxx
Now if you convert 49765 to binary, you get
11000010 01100101
which clearly dows not match this pattern.
Yours,
Laurenz Albe
Received on Wed Jan 14 2009 - 04:11:43 CST