-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/6/12 6:51 AM, Joe Hildebrand (jhildebr) wrote: > On 11/2/12 8:05 PM, "Peter Saint-Andre" <[email protected]> > wrote: > >> Ask, and ye shall receive. >> >> ### >> >> For comparison purposes (e.g., when a chatroom server determines >> if two nicknames are in conflict during the authorization >> process), an application MUST treat a nickname as follows, where >> the operations specified MUST be completed in the order shown (in >> particular, normalization MUST be performed before all other >> mapping steps and validity checks, consistent with >> [I-D.ietf-precis-framework]): >> >> 1. The string MUST be normalized using Unicode Normalization >> Form KC (NFKC). Because NFKC is more "aggressive" in finding >> matches than other normalization forms (in the terminology of >> Unicode, it performs both canonical and compatibility >> decomposition before recomposing code points), this rule helps to >> reduce the possibility of confusion by increasing the number of >> characters that would match (e.g., U+2163 ROMAN NUMERAL FOUR >> would match the combination of U+0049 LATIN CAPITAL LETTER I and >> U+0056 LATIN CAPITAL LETTER V). >> >> 2. Uppercase and titlecase characters MUST be mapped to their >> lowercase equivalents. In applications that prohibit >> conflicting nicknames, this rule helps to reduce the possibility >> of confusion by ensuring that nicknames differing only by case >> (e.g., "stpeter" vs. "StPeter") would not be allowed in a >> chatroom at the same time. >> >> 3. Non-ASCII space characters from the "N" category defined >> under Section 6.14 of [I-D.ietf-precis-framework] MUST be mapped >> to U+0020 SPACE. >> >> 4. Leading and trailing whitespace (i.e., one or more instances >> of the ASCII space character at the beginning or end of a >> nickname) MUST be removed (e.g., "stpeter " is mapped to >> "stpeter"). >> >> 5. Interior sequences of more than one ASCII space character >> MUST be mapped to a single ASCII space character (e.g., "St >> Peter" is mapped to "St Peter"). >> >> 6. Other mappings MAY be applied, such as those defined in >> [I-D.yoneya-precis-mappings]. (Note that mapping of fullwidth >> and halfwidth characters to their decomposition mappings is not >> necessary, since those mappings are performed as part of >> normalization using NFKC.) > > I think we should also add the confusable mapping (see: > http://www.unicode.org/reports/tr39/#Confusable_Detection) here.
Based on discussion during the WG session today, I'd say we didn't have agreement to go down that path, at least not for this specification. Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlCZ6DMACgkQNL8k5A2w/vyNggCg2Xwu596MfIqKdMcnrI1jg8FP 35YAnRGhmVqBJy+TGJ9ieXuZTey0WgjX =FP5V -----END PGP SIGNATURE----- _______________________________________________ precis mailing list [email protected] https://www.ietf.org/mailman/listinfo/precis
