Can NFKC turn valid UAX 31 identifiers into non-identifiers?

Manish Goregaokar via Unicode unicode at
Mon Jun 4 14:49:20 CDT 2018


The Rust community is considering
<> adding non-ascii identifiers,
which follow UAX #31 <> (XID_Start
XID_Continue*, with tweaks). The proposal also asks for identifiers to be
treated as equivalent under NFKC.

Are there any cases where this will lead to inconsistencies? I.e. can the
NFKC of a valid UAX 31 ident be invalid UAX 31?

(In general, are there other problems folks see with this proposal?)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Unicode mailing list