On 2/13/17 12:04 AM, William Fisher wrote: > On Sun, Feb 12, 2017 at 12:27 PM, Peter Saint-Andre <stpe...@stpeter.im> > wrote: >> Did you mean U+212A (KELVIN SIGN)? That decomposes to U+004B (LATIN CAPITAL >> LETTER K). >> >>> The full example is: >>> "\U0001f11aevin" => "(K)evin" => "(k)evin" > > I'm talking about 'PARENTHESIZED LATIN CAPITAL LETTER K' (U+1F11A). > Sorry it's not clear that the A is part of the unicode escape.
Thanks for the clarification. > With casefold or tolower, the result is the same for these Nicknames: > > Not idempotent: "\U0001f11A" => "(K)" => "(k)" > Not idempotent: "\U0001f13A" => "K" => "k" > Not idempotent: "\u210c" => "H" => "h" > Not idempotent: "\u210d" => "H" => "h" > Not idempotent: "\u20a8" => "Rs" => "rs" > > When you apply the comparison steps from RFC 7700, Section 2.4, you > still get something that is upper case. If you apply the comparison > steps again, you now get lower case. I see what you mean. I'm now leaning toward moving the case mapping rule after the normalization rule, but first I want to think about the implications for all of the PRECIS profiles (e.g., when using NFC vs. using NFKC). If we go down this road, we will also want to describe the reasoning in Section 5.2.3 of 7564bis. Peter _______________________________________________ precis mailing list precis@ietf.org https://www.ietf.org/mailman/listinfo/precis
