- From: vyv03354 <notifications@github.com>
- Date: Fri, 05 May 2017 18:18:47 -0700
- To: whatwg/encoding <encoding@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Saturday, 6 May 2017 01:19:24 UTC
Can the index deal with composing? For example, will U+FF76 U+FF9E ("ガ") be converted to U+30AC ("ガ") instead of U+30AB U+309B ("カ゛")? At least Gecko will convert it to U+30AC. I don't know about Blink nor Edge. Probably this is the reason why NFKC uses combining characters despite that no Japanese legacy encodings have them. But if U+3099 or U+309A is left after conversion, they should be converted to U+309B or U+309C, respectively. -- 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-299606565
Received on Saturday, 6 May 2017 01:19:24 UTC