26886 2014-09-22 17:51:14 +0000 JIS X 201 vs US-ASCII in ISO-2022-JP 2014-11-06 10:44:41 +0000 1 1 1 Unclassified WHATWG Encoding unspecified All All RESOLVED DUPLICATE 27256 P2 normal Unsorted 16685 1 jshin annevk hsivonen jsbell mike pub-w3 smontagu travil VYV03354 www-international sideshowbarker+encodingspec oldest_to_newest 111952 0 jshin 2014-09-22 17:51:14 +0000 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 ? 111972 1 annevk 2014-09-22 19:25:21 +0000 Adding those that know Gecko. Perhaps Opera Presto had this behavior? Or IE? 111985 2 smontagu 2014-09-22 22:28:15 +0000 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) 114491 3 annevk 2014-11-04 15:12:32 +0000 It's not entirely clear to me how we want to proceed here. 114596 4 annevk 2014-11-06 10:44:41 +0000 *** This bug has been marked as a duplicate of bug 27256 ***