----- Original Message ----- From: "Martin Duerst" <[EMAIL PROTECTED]> To: "Soobok Lee" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Friday, October 19, 2001 5:26 PM Subject: Re: [idn] call for comments for REORDERING
> At 15:43 01/10/10 +0900, Soobok Lee wrote: > > >From: "Martin Duerst" <[EMAIL PROTECTED]> > > > > The additional complexity introduced by reordering is a very > > > serious problem. It is true that this complexity is somewhat > > > similar to the complexity of e.g. nameprep or conversion from > > > a legacy encoding. However, on many platforms, both conversion > > > from a legacy encoding as well as many aspects of nameprep > > > are available as libraries, and are used for other purposes. > > > >Current Windows 98,2K,XP and Linux contain NFKC codes ? > > No. My personal preference would be for NFC, anyway, because > most of the additional mappings in NFKC are not really useful, > because they are from characters that are quite difficult > to type in. So these characters could just be forbidden rather > than mapped. The only exception I know is full-width ASCII, > which could either be included in the nameprep mapping step, > or could be done as a front-end 'quality of implementation' > step (similar to how the ideographic fullstop is currently > treated). My personal preference is NFKC. Because it solves the mappings between the extended han ideographic block and han ideo block. > > Anyway, it's not so much a question of whether current versions > contain that code (there are libraries that do), but how much > other software will use it. There will definitely be other > software that uses NFC, and quite probably also NFKC. > This is not at all the case for reordering. > > I expect REODERING+ACE may be used also in mailbox name part in IDN email addressess. What if the reordering table will find many other internet applications in the future like NFC/NFKC. No one knows. Soobok Lee
