- From: <bugzilla@jessica.w3.org>
- Date: Mon, 22 Sep 2014 17:35:26 +0000
- To: www-international@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26885 Bug ID: 26885 Summary: Drop JIS X 212 from ISO-2022-JP Product: WHATWG Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P2 Component: Encoding Assignee: annevk@annevk.nl Reporter: jshin@chromium.org QA Contact: sideshowbarker+encodingspec@gmail.com CC: mike@w3.org, www-international@w3.org EUC-JP in the encoding spec does not support JIS X 212 even though the formal definition of EUC-JP does include it. OTOH, ISO-2022-JP in the encoding spec does support JIS X 212 to my surprise. Is there a reason to support JIS X 212 in ISO-2022-JP? It's not a part of the original ISO-2022-JP (RFC 1468 : https://www.ietf.org/rfc/rfc1468.txt). It's added later in RFC 1554, but I don't think it's widely used. Blink has never supported ISO-2022-JP-2 with JIS X 212. It only supports the original ISO-2022-JP. Supporting JIS X 212 adds ~ 50kB to our build and I'd rather avoid it. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Monday, 22 September 2014 17:35:28 UTC