ISSUE-453: Bring back gbk encoder

Bring back gbk encoder

State:
CLOSED
Product:
encoding
Raised by:
Richard Ishida
Opened on:
2015-03-30
Description:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27235

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

https://bugzilla.mozilla.org/show_bug.cgi?id=951691#c16
https://bugzilla.mozilla.org/show_bug.cgi?id=951691#c19

Having said that, if other browsers meanwhile converged on not having a
distinct gbk encoder, perhaps Firefox should revisit its approach. Input
welcome.
Related Actions Items:
No related actions
Related emails:
  1. I18N-ISSUE-453 (BUG27235): Bring back gbk encoder [encoding] (from sysbot+tracker@w3.org on 2015-03-30)

Related notes:

These issues are now tracked at http://www.w3.org/International/docs/encoding/encoding-cr-doc

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

Display change log ATOM feed


Addison Phillips <addison@amazon.com>, Chair, Richard Ishida <ishida@w3.org>, Fuqiao Xue <xfq@w3.org>, Atsushi Shimono <atsushi@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $