[Bug 26885] Drop JIS X 212 from ISO-2022-JP

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

--- Comment #5 from Jungshik Shin <jshin@chromium.org> ---
Well, the way ICU's ISO-2022-JP-2 implementation is written, the JIS X 212
table is not shared with EUC-JP converter. Unless I change the ICU to share JIS
X 212 table, Blink has to live with the build size increase of tens of kBs. 

In addition, I have to change it unidirectional (decoding only). 

These are doable, but it's not clear if there's any user-benefits other than
being compliant to the current spec. 

With "ISO-2022-JP" label, Blink (Chrome, Opera) and Safari do not support JIS X
212. They never did (except that I don't know whether the old Opera ever did). 

With "ISO-2022-JP-1" (or ISO-2022-JP-2) label, Blink and Safari do support JIS
X 212 in both directions. Needless to say, virtually nobody uses
'ISO-2022-JP-[12]' in charset declaration. So, it does not count. 

MSIE does not support JIS X 212 either in ISO-2022-JP. 

That leaves only Firefox supporting JIS X 212 in ISO-2022-JP at the moment.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Wednesday, 24 September 2014 17:24:16 UTC