On Mar 3, 2008, at 6:11 PM, Jjgod Jiang wrote:
in their header, yet they might use characters in GBK but
not in GB2312. So, I think we can suggest clients to simply
treat encodings like these as their biggest superset, for
instance, treat GB2312 as GB18030.
BTW, browsers like Firefox seems already handles such cases
well, but Safari/WebKit seems not.
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.
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.
- WBR, Alexey Proskuryakov
