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

I18N-ISSUE-441 (BUG26885): Drop JIS X 212 from ISO-2022-JP [encoding]

From: Internationalization Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Mon, 30 Mar 2015 13:51:14 +0000
To: public-i18n-core@w3.org
Message-Id: <E1Yca5y-0007tT-0V@maia.w3.org>
I18N-ISSUE-441 (BUG26885): Drop JIS X 212 from ISO-2022-JP [encoding]

http://www.w3.org/International/track/issues/441

Raised by: Richard Ishida
On product: encoding

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23650

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

---

Reporter: jshin@chromium.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.
Received on Monday, 30 March 2015 13:51:18 UTC

This archive was generated by hypermail 2.3.1 : Monday, 30 March 2015 13:51:18 UTC