ISSUE-453: Bring back gbk encoder

Bring back gbk encoder

Raised by:
Richard Ishida
Opened on:

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



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 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
Related Actions Items:
No related actions
Related emails:
  1. I18N-ISSUE-453 (BUG27235): Bring back gbk encoder [encoding] (from on 2015-03-30)

Related notes:

These issues are now tracked at

Richard Ishida, 16 Sep 2015, 11:44:21

Display change log ATOM feed

Addison Phillips <>, Chair, Richard Ishida <>, Bert Bos <>, Fuqiao Xue <>, Atsushi Shimono <>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $