We (KRNIC NC) found a KC normalization implementation
in nameprep-03 does not preserve
the hangul compatibility jamo character sequences,
but combines them into hangul syllables with errornously leaving
jongseong jamo behind (CVL -> (CV)(L) [false], (CVL) is right).
I think we may consider taking away this hangul combining actions
from nameprep-implementation of KC normalization.
and more work should be done on whether to prohibit
the 4 hangul filler characters,
and on case-folding of hangul jamo characters in 4 forms
(choseong,jongseong,compatibility jamo,narrow-form).
we are studying the ambiguity that may arise between hangul and
many other language character sets. Japanese katakana 'ro' and
hangul jamo 'mieum' look the same!
If multilingual names are introduced in [EMAIL PROTECTED], http://ML.com,
this ambiguity issues become the internet security issues, i am afraid.
We'll continue to follow up IDN wg's nameprep efforts and submit a
draft if necessary.
Soobok Lee
[EMAIL PROTECTED]
----- Original Message -----
From: "Paul Hoffman / IMC" <[EMAIL PROTECTED]>
To: "Adam M. Costello" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Friday, June 01, 2001 12:38 PM
Subject: Re: [idn] nameprep
> At 3:07 AM +0000 6/1/01, Adam M. Costello wrote:
> >Paul Hoffman / IMC <[EMAIL PROTECTED]> wrote:
> >
> >> need to finish nameprep, which at this point is finished other than it
> >> does not address the new characters added in Unicode 3.1.
> >
> >Nameprep currently includes the following steps:
> >
> > KC-normalize
> > map
> > KC-normalize
> > prohibit
>
> Er, no it doesn't. It only includes map->normalize->prohibit.
>
> --Paul Hoffman, Director
> --Internet Mail Consortium
>
