Re: [idn] call for comments for REORDERING

["Soobok Lee" <lsb@postel.co.kr>]

----- Original Message ----- 
From: "Martin Duerst" <duerst@w3.org>
To: "Soobok Lee" <lsb@postel.co.kr>; "James Seng/Personal" <jseng@pobox.org.sg>; <idn@ops.ietf.org>
Sent: Friday, October 19, 2001 6:09 PM
Subject: Re: [idn] call for comments for REORDERING


> At 17:48 01/10/19 +0900, Soobok Lee wrote:
> 
> >----- Original Message -----
> >From: "Martin Duerst" <duerst@w3.org>
> > > Also, in case of some implementation mistake in Nameprep/NFKC,
> > > in most cases, it will just make a few names unusable, but
> > > not affect the rest. For reordering, a bug will completely
> > > confuse a whole script.
> >
> >Never.
> >REoredering does not touch on unassigned code points at all.
> >REORDERING is idempotent  for unassigned code points.
> 
> I didn't talk about unassigned code points.
> What I mean is this: If you have two frequency tables,
> and they differ by e.g. one forgetting a particular
> character, then virtually all your compressed results
> are different. If you have a wrong mapping in a
> NFC or NFKC algorithm, then only that character is
> affected.

Never. The REORDERING table for a script has *NO*
missing characters because it applies idempotent
mappings for even unassigned code points.

For one ACE prefix, one fixed reordering table!

If we should change the frequency table, new versioning
prefix should be introduced to avoid conflicts in the same
time when there is need to make major modifications to 
NFC/NFKC due to erros in them. 
If version 1 has "dq--" prefix, version 2 should have
other ones like "xq--". Reordering tables could be
improved at that time if needed.


SOobok Lee