>To: Dan Oscarsson <[EMAIL PROTECTED]> >Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] >Subject: Re: Is space allowed in a hostname? >X-Hashcash: 020709:[EMAIL PROTECTED]:6a0136bb72edce86 >X-Hashcash: 020709:[EMAIL PROTECTED]:43f94292c523c78c >X-Hashcash: 020709:[EMAIL PROTECTED]:4f511128bbb871d5 >X-Hashcash: 020709:[EMAIL PROTECTED]:ed630ef750c2ac24 >From: Simon Josefsson <[EMAIL PROTECTED]>
>Since NFKC is used in stringprep too, this is not only for domain >names but internationalized strings in many environments (such as >authentication identities and passwords). The use of NFKC is optional >in stringprep though, but the alternative is to use no normalization >at all. > >Stringprep furthermore warns profile authors against using the >no-normalization alternative because it may confuse users. In all >honesty, I think stringprep should also say that using NFKC may also >confuse users, altough perhaps different users and different kind of >confusion. > I do not know why stringprep only have NFKC or unnormalised as possible choices. NFC is a very suitable choice to use for UCS. It is the choice of W3C and is the required choice in IRI/URIs. NFC have the nice properties that it preserves all information and is compact. It is a very good choice to use for interoperability. Unnormalised is only useful locally on a system, never for interoperability. NFKC is a possible choice when matching text but may go to far when related to identifiers (names). Dan
