W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2008

[whatwg] A comment to character encoding declaration

From: Jjgod Jiang <gzjjgod@gmail.com>
Date: Fri, 7 Mar 2008 16:12:30 +0800 (CST)
Message-ID: <alpine.OSX.1.00.0803071605350.452@epicalyx.local>
Hi Alexey,

On Fri, 7 Mar 2008, Alexey Proskuryakov wrote:
>   In my testing, it appears that IE 7 and Firefox 2 do treat GBK as 
> an equivalent of GB2312, but this cannot be said about GB18030. In 
> particular, 0x80 and 0xA2E3 are treated differently.

Yep, I missed that point in my previous post, my fault. Yes, they
should be treated differently. So I guess my request should be changed
to only treat GB2312 as GBK.

>   See:
> <http://nypop.com/~ap/webkit/gbk.html>
> <http://nypop.com/~ap/webkit/gb18030.html>
>
>   What differences are you seeing between Firefox and WebKit? It 
> seems that the behavior may be a bit more tricky than just treating 
> all encodings from GBK family as GB18030.

On Safari 3.0.4, only 0x80 is recognized as euro mark in gbk.html,
and only 0xA2E3 is recognized as euro mark in gb18030.html. But on
Firefox 3.0 (Gecko/2008030604 nightly build), both 0x80 and 0xA2E3
is recognized as euro mark in gb18030.html. So there seems to be
some inconsistencies here, and I think you're right, simply treat
all GBK family encodings as GB18030 is not a good idea.

- Jiang
Received on Friday, 7 March 2008 00:12:30 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:40 UTC