----- Original Message ----- From: "Martin Duerst" <[EMAIL PROTECTED]> > > >Current IDNA/nameprep does not prohibit, but discourage including > >unassigned code points in legal IDN labels, because new normalization/case > >mappings > >would be defined on them in the future. some ACE labels including unsigned > >code block (tagalog?) might be proven invalid in the future. Nameprep/NFKC > >Versioning tag schems using new ACE prefix will be needed in the future, i > >guess. > > Yes. But for the majority of really useful characters, in old > and new scripts, it's rather obvious that they will be allowed. > On the other hand, it's totally unclear how to reorder them. > > 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. > > Also, now we have a testbed, and you just think that the testbed > is representative. But once IDN is running, to run a testbed > for a new script will be difficult, because we need the testbed > data for the reordering statistics, but we need the reordering > for the testbed. > 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. Soobook Lee
