W3C home > Mailing lists > Public > www-international@w3.org > October to December 2014

[Bug 27235] Bring back gbk encoder

From: <bugzilla@jessica.w3.org>
Date: Mon, 10 Nov 2014 07:01:18 +0000
To: www-international@w3.org
Message-ID: <bug-27235-4285-jwalbLpEaN@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27235

--- Comment #4 from Jungshik Shin <jshin@chromium.org> ---
Sorry that I didn't get back here in a timely manner. I was out on
internal/external conferences last week. Chromium was hesitant, but I've been
considering merging gbk and gb18030 per spec before the latest revision. 

Moreover, latest revision made it a bit hard to implement GBK/GB18030 without
touching the ICU's gb18030 implementation (even though I agree to the approach;
1. decoding is identical for both encodings 2. gbk encoding is limited to 'the
gbk subset').  I've just read the latest revision and it's just my first
thought. There might be an easier way. I'll give more thought to it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 10 November 2014 07:01:20 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 September 2016 22:37:38 UTC