ISSUE-442: JIS X 201 vs US-ASCII in ISO-2022-JP

JIS X 201 vs US-ASCII in ISO-2022-JP

State:
CLOSED
Product:
encoding
Raised by:
Richard Ishida
Opened on:
2015-03-30
Description:
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 ?
Related Actions Items:
No related actions
Related emails:
  1. I18N-ISSUE-442 (BUG26886): JIS X 201 vs US-ASCII in ISO-2022-JP [encoding] (from sysbot+tracker@w3.org on 2015-03-30)

Related notes:

Bug marked DUPLICATE of https://www.w3.org/Bugs/Public/show_bug.cgi?id=27256

Richard Ishida, 30 Mar 2015, 13:59:49

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

Richard Ishida, 16 Sep 2015, 11:54:48

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 $