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

I18N-ISSUE-442 (BUG26886): JIS X 201 vs US-ASCII in ISO-2022-JP [encoding]

From: Internationalization Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Mon, 30 Mar 2015 13:59:10 +0000
To: public-i18n-core@w3.org
Message-Id: <E1YcaDe-000G3T-PS@deneb.w3.org>
I18N-ISSUE-442 (BUG26886):  JIS X 201 vs US-ASCII in ISO-2022-JP  [encoding]

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

Raised by: Richard Ishida
On product: encoding

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

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

---

Reporter: jshin@chromium.org

Blink (Chrome, Opera) and Webkit with ICU (Safari) distinguish between JIS X
201 ( "ESC ( J") and US-ASCII ( "ESC ( B" ). I thought that Gecko did that, too
even though it may have changed its behavior recently to match the spec. 

Assuming that Gecko did distinguish between the two in the past, what's the
rationale for unifying the two given the status of implementations ?
Received on Monday, 30 March 2015 13:59:13 UTC

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