[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[idn] Re: [idn] Namprep-02: ß.com



I agree that the wording in that section needs some cleanup. Just in case it
is not clear, the CaseFolding tables are part of the UCD. They are currently
in beta (although at this point it would require a special letter ballot to
change them); they will be final by the end of March.

> This makes it easier to see that this is NOT a simple conversion to
lowercase.
> (there was no

Looks like this message was cut off.

Mark
----- Original Message -----
From: "Harald Alvestrand" <Harald@Alvestrand.no>
To: "Mark Davis" <mark@macchiato.com>; "Rick H Wesson" <wessorh@ar.com>;
"Paul Hoffman / IMC" <phoffman@imc.org>
Cc: <idn@ops.ietf.org>
Sent: Sunday, February 04, 2001 19:41
Subject: Re: [idn] Namprep-02: ß.com


> At 09:30 04/02/2001 -0800, Mark Davis wrote:
> >The source documents to look at are:
> >
> >http://www.unicode.org/Public/3.1-Update/CaseFolding-3d4.beta.txt
> >
> >http://www.unicode.org/unicode/reports/tr21/
> >
> >There it explains the treatment of es-zed.
>
> gotcha.
>
> what I missed was that this section:
>
> >3.1 Case mapping
> >
> >For each character in the input, if there is a lowercase mapping for
> >that character, the input character is changed to the mapped lowercase
> >character(s). The entries in the mapping table are derived from [UTR21].
>
> could have read:
>
> The input string is case folded according to [UTR21] section 2.3.
> For most cases, this is the same thing as changing the input character to
a
> lowercase character; however, for some cases more complex things happen.
> The mapping table in appendix N is used. This is derived from [UTR21] by
> applying the rules for equivalence classes of section 2.3
>
> This makes it easier to see that this is NOT a simple conversion to
lowercase.
> (there was no
>
> --
> Harald Tveit Alvestrand, alvestrand@cisco.com
> +47 41 44 29 94
> Personal email: Harald@Alvestrand.no
>
>
>