- From: <bugzilla@jessica.w3.org>
- Date: Thu, 28 May 2015 05:11:31 +0000
- To: www-international@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28661 --- Comment #12 from Jungshik Shin <jshin@chromium.org> --- (In reply to Masatoshi Kimura from comment #9) > Created attachment 1604 [details] > encoding-only mappings found on Chrome > > Looks like Chrome also has some bugs... These and a number of other entries do not make any sense. (I'm aware that your test script generated them. ) euc-kr: ffe0(￠)=>ffe1(￡) euc-kr: ffe1(￡)=>ffe2(￢) euc-kr: ffe2(￢)=>ffe3(￣) euc-kr: ffe4(￤)=>ffe5(￥) euc-kr: ffe5(￥)=>ffe6(￦) Chrome's EUC-KR table does not have any one-way mapping in either direction. See https://code.google.com/p/chromium/codesearch#chromium/src/third_party/icu/source/data/mappings/euc-kr-html.ucm&q=euc&sq=package:chromium&l=1 One way mapping should have '|1' or '|3' at the end of each entry. BTW, GBK is not yet aligned with the spec. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Thursday, 28 May 2015 05:11:34 UTC