Can NFKC turn valid UAX 31 identifiers into non-identifiers?
Manish Goregaokar via Unicode
unicode at unicode.org
Mon Jun 4 14:57:16 CDT 2018
Oh, looks like UAX 31 has info on how to be closed under NFC
On Mon, Jun 4, 2018 at 12:49 PM Manish Goregaokar <manish at mozilla.com>
> The Rust community is considering
> <https://github.com/rust-lang/rfcs/pull/2457> adding non-ascii
> identifiers, which follow UAX #31 <http://www.unicode.org/reports/tr31/>
> (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...
More information about the Unicode