Re: [idn] Re: stringprep and unassigned code points

[YangWoo Ko <newcat@spsoft.co.kr>]

Dear Patrik Falstrom,

Thank you for your clear summary. Exeucuse me but would you do the
summary again for the following case ? This is really helpful when
we talk about Traditional Chinese / Simplified Chinese issue.

If a new version of Unicode comese out, which have a newly defined
rule to map codepoint (X) to codepoint (Y), where codepoint (X)
and (Y) was already defined in the previous version of Unicode and
there no rule for mapping or NF?C for either codepoint(X) or
codepoint(Y), the following is true:

...

On Thu, Oct 25, 2001 at 11:10:58AM +0200, Patrik Fältström wrote:
> Summary (once again):
> 
> If a new version of Unicode comes out, which have a newly assigned
> codepoint (X), and a mapping from X to Y, the following is true:
> 
> - X can not be part of the result of a nameprep which an old application
>   creates. If an old application get X as input, the codepoint is unassigned
>   and therefore illegal.
> - If Y is an earlier assigned codepoint, an application understanding the
>   new version of nameprep will when getting X map that to Y.
> - If Y is a newly assigned codepoint, an application understanding the
>   new version of nameprep will when getting X map that to Y.
> - In neither case (old application or new application) X will be part of
>   the output of the stringprep process.

-- 
/*------------------------------------------------
YangWoo Ko : newcat@spsoft.co.kr
We Invent Enterprise Software Solutions
and Make You Secure & Powerful.
------------------------------------------------*/