Requiring typed text to be NFKC (was: Can NFKC turn valid UAX 31 identifiers into non-identifiers?)

From: Manish Goregaokar via Unicode <>
Date: Tue, 5 Jun 2018 19:48:53 -0700

Following up from my previous email
<>, one of
the ideas that was brought up was that if we're going to consider NFKC
forms equivalent, we should require things to be typed in NFKC.

I'm a bit wary of this. As Richard brought up in that thread, some Thai
NFKC forms are untypable. I *suspect* there are Hangul keyboards (perhaps
physical non-IME based ones) that have this problem.

Do folks have other examples? Interested in both:

 - Words (as in, real things people will want to type) where a keyboard/IME
does not type the NFKC form
 - Words where a keyboard/IME *can* type the NFKC form but users are not
used to it
 - Words where the NFKC form is *visually* distinct enough that it will
look weird to native speakers

Received on Tue Jun 05 2018 - 21:49:29 CDT

This archive was generated by hypermail 2.2.0 : Tue Jun 05 2018 - 21:49:30 CDT