This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 26886 - JIS X 201 vs US-ASCII in ISO-2022-JP
Summary: JIS X 201 vs US-ASCII in ISO-2022-JP
Status: RESOLVED DUPLICATE of bug 27256
Alias: None
Product: WHATWG
Classification: Unclassified
Component: Encoding (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+encodingspec
URL:
Whiteboard:
Keywords:
Depends on: 16685
Blocks:
  Show dependency treegraph
 
Reported: 2014-09-22 17:51 UTC by Jungshik Shin
Modified: 2014-11-06 10:44 UTC (History)
8 users (show)

See Also:


Attachments

Description Jungshik Shin 2014-09-22 17:51:14 UTC
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 ?
Comment 1 Anne 2014-09-22 19:25:21 UTC
Adding those that know Gecko. Perhaps Opera Presto had this behavior? Or IE?
Comment 2 Simon Montagu 2014-09-22 22:28:15 UTC
AFAIK Gecko has always treated JIS X 201 Roman set and US-ASCII as identical (but see the code comment at http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/intl/uconv/ucvja/nsJapaneseToUnicode.cpp&rev=1.2&mark=643-645#634)
Comment 3 Anne 2014-11-04 15:12:32 UTC
It's not entirely clear to me how we want to proceed here.
Comment 4 Anne 2014-11-06 10:44:41 UTC

*** This bug has been marked as a duplicate of bug 27256 ***