[Bug 28156] Separate GBK and GB18030 even for decoding (toUnicode)

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28156

--- Comment #5 from Jungshik Shin <jshin@chromium.org> ---
(In reply to Jungshik Shin from comment #4)
> Hmm.. What's required for ICU can be simpler than I thought (without
> actually looking) if we *only* care about the conversion and might be
> acceptable by the upstream. In that case, we can save almost 100kB (by
> dropping the GBK table entirely). A strawman CL for Chrome's ICU is at
> https://codereview.chromium.org/1141463003/. I haven't even compiled it,
> though.

Well, it's not that simple.  It'd be better to do that in Blink. 

However, I think the spec had better be changed to separate GBK and GB18030
completely (in both directions). 

Unlike other pairs or triplets which the spec made synonymous with each other,
I don't believe that GBK and GB18030 were used synchronously in the wild partly
because none of widely used browsers has treated them as synonyms until Firefox
did per the spec recently.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Friday, 29 May 2015 22:00:52 UTC