- From: <bugzilla@jessica.w3.org>
- Date: Tue, 04 Nov 2014 19:43:19 +0000
- To: www-international@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27235 Bug ID: 27235 Summary: Bring back gbk encoder Product: WHATWG Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: Encoding Assignee: annevk@annevk.nl Reporter: annevk@annevk.nl QA Contact: sideshowbarker+encodingspec@gmail.com CC: hsivonen@hsivonen.fi, jsbell@google.com, jshin@chromium.org, mike@w3.org, travil@microsoft.com, www-international@w3.org 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. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Tuesday, 4 November 2014 19:43:20 UTC