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

On Mon, 4 Jun 2018 12:49:20 -0700 Manish Goregaokar via Unicode wrote: > Hi, > > The Rust community is considering > adding non-ascii > identifiers, which follow UAX #31 > (XID_Start XID_Continue*, with > tweaks

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

On 6/6/2018 2:25 PM, Hans Åberg via Unicode wrote: On 4 Jun 2018, at 21:49, Manish Goregaokar via Unicode wrote: The Rust community is considering adding non-ascii identifiers, which follow UAX #31 (XID_Start XID_Continue*, with tweaks). The propo

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

> On 4 Jun 2018, at 21:49, Manish Goregaokar via Unicode > wrote: > > 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. So, in this l

Re: Requiring typed text to be NFKC

On Tue, 5 Jun 2018 19:48:53 -0700 Manish Goregaokar via Unicode wrote: > 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

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

On Mon, Jun 4, 2018 at 10:49 PM, Manish Goregaokar via Unicode wrote: > The Rust community is considering adding non-ascii identifiers, which follow > UAX #31 (XID_Start XID_Continue*, with tweaks). UAX #31 is rather light on documenting its rationale. I realize that XML is a different case from

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

It could be argued that "modern" languages could use unique identifiers for their syntax or API independantly of the name being rendered. The problem is that translated names may collide in non-obvious way and become ambiguous. We've already seen the problems it caused in Excel with its translated

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

On 5 Jun 2018, at 07:09, Martin J. Dürst via Unicode wrote: > > Hello Rebecca, > > On 2018/06/05 12:43, Rebecca T via Unicode wrote: > >> Something I’d love to see is translated keywords; shouldn’t be hard with a >> line in the cargo.toml for a ruidmentary lookup. Again, I’m of the opinion >>

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

On 4 Jun 2018, at 20:49, Manish Goregaokar via Unicode wrote: > > 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 c