- From: Anne van Kesteren <notifications@github.com>
- Date: Fri, 05 May 2017 22:24:25 -0700
- To: whatwg/encoding <encoding@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Saturday, 6 May 2017 05:24:59 UTC
> Can the index deal with composing? An index would not be able to do that. Neither Chromium nor WebKit have such behavior, due to ICU lacking it: http://searchfox.org/mozilla-central/source/intl/icu/source/common/ucnv2022.cpp#1597 (this code is not actually used by Firefox as I initially thought). Edge does not have this behavior either, which I checked with https://dump.testsuite.org/encoding/iso-2022-jp/encode.html as Henri's tool doesn't work in Edge. The code for Firefox is at http://searchfox.org/mozilla-central/source/intl/uconv/ucvja/nsUnicodeToISO2022JP.cpp which has `gBasicMapping` taking care of the "index" (I suspect this is where I got "basics" from in the web-platform-tests regression Henri found) and `ConvertHankaku` that deals with the modifiers. Neither code references NFKC (and the way I used NFKC wouldn't do the combining either). I would suggest we don't keep the combining behavior given these results. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/encoding/pull/106#issuecomment-299616944
Received on Saturday, 6 May 2017 05:24:59 UTC