W3C home > Mailing lists > Public > public-i18n-core@w3.org > January to March 2015

I18N-ISSUE-453 (BUG27235): Bring back gbk encoder [encoding]

From: Internationalization Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Mon, 30 Mar 2015 14:41:43 +0000
To: public-i18n-core@w3.org
Message-Id: <E1Ycasp-0009PH-8q@maia.w3.org>
I18N-ISSUE-453 (BUG27235): Bring back gbk encoder [encoding]


Raised by: Richard Ishida
On product: encoding


This issue tracks the bug listed above and was created as part of the WG CR process.


Reporter: annevk@annevk.nl

Firefox ended up not following the plan from bug 16862 comment 18. Its gbk
decoder is identical to its gb18030 decoder, but its gbk encoder per
https://bugzilla.mozilla.org/show_bug.cgi?id=951691 is distinct.

So we should probably bring the gbk encoder back. When fixing this we should
pay attention to the EURO sign and PUA code points. See


Having said that, if other browsers meanwhile converged on not having a
distinct gbk encoder, perhaps Firefox should revisit its approach. Input
Received on Monday, 30 March 2015 14:41:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:02:05 UTC