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

From: Manish Goregaokar via Unicode <>
Date: Mon, 4 Jun 2018 12:49:20 -0700


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?)

Received on Mon Jun 04 2018 - 14:50:02 CDT

This archive was generated by hypermail 2.2.0 : Mon Jun 04 2018 - 14:50:03 CDT