At 17:48 01/10/19 +0900, Soobok Lee wrote: >----- Original Message ----- >From: "Martin Duerst" <[EMAIL PROTECTED]> > > 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. >Optimal frequency table does not exist now and future and forever. >sub-optimal solutions are often very useful and accepted and >REORDERING is just one of them. ACE-Z without reordering is also a sub-optimal solution. I propose that we just use it. Regards, Martin.
