Re: [idn] Re: Back to work (Nameprep) (was: Re: Just send UTF-8 with nameprep (was: RE: [idn] Reality Check))

["tsenglm" <tsenglm@cc.ncu.edu.tw>]

----- Original Message -----
From: "Keith Moore" <moore@cs.utk.edu>
To: "Soobok Lee" <lsb@postel.co.kr>
Cc: "Keith Moore" <moore@cs.utk.edu>; "Martin Duerst" <duerst@w3.org>;
<idn@ops.ietf.org>
Sent: Wednesday, July 18, 2001 11:10 PM
Subject: Re: [idn] Re: Back to work (Nameprep) (was: Re: Just send UTF-8
with nameprep (was: RE: [idn] Reality Check))


> > Now, let's think about another case of   all-Greek "oo.com" and
all-Latin
> > "oo.com":
> > Either of the two consists of scripts from only single character sets.
> > But the two still look very similiar. Do you have any good idea about
this ?
>
Assume there are no mixed type of language scripts  except the ASCII.
At client side , the input method environment knows what language the user
used.
To differentiate them ,   a lookup table can be  used , they can be
represented as:
      Greek(oo.com)  => unicode(oo).greek.com
      Latin(oo.com)   =>  unicode(oo).latin.com

Just like ACE is mapped to  ASCII LDH, so ACE(IDN)  need  bq--  tag for IDN
to differentiate them from traditional ascii domain-name.

Li-Ming Tseng,