[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] UTF-8 / RACE
- To: "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>
- Subject: Re: [idn] UTF-8 / RACE
- From: "James Seng/Personal" <James@Seng.cc>
- Date: Wed, 30 May 2001 09:47:01 +0800
- Delivery-date: Tue, 29 May 2001 18:48:21 -0700
- Envelope-to: idn-data@psg.com
> Read the page: ``An uppercase ... is guaranteed to cause confusion:
when
> the uppercase Alpha is printed properly, it looks just like an
uppercase
> A. Some other strings are also guaranteed to cause confusion. There's
a
> complicated definition of good names among all Unicode strings. Good
> names won't be confused with each other. Registrars won't allow
> registration of bad names.''
So you mean I could only have "françious" but could never "FRANÇIOUS"?
What if due to my personal preference/trademark, I want to have
uppercase char? To draw an english analogy, try "IBM" or "eBay" or "AOL"
or ...
> Good names are the same concept as the output of nameprep, except that
> the current nameprep specification is flawed---it doesn't handle
Alpha,
> for example.
In other words, there would be a routine to create 'good' names. It may
be less complex than the current Nameprep but there will be.
> > It is too early to suspect how I18N Email will look like to decide
> > what changes would be required in sendmail but I suspect making it
8-bit
> > clean as you suggested here is probably needed if UTF-8 are use in
IDN.
>
> You are confused. The changes I specified are necessary and
sufficient.
I dont think I am confused. I am just not ready to do I18N Email right
now.
Your current implict proposal is to do it by pushing UTF-8 thru SMTP and
I am not ready to conclude this is right way.
> > But most important of all, you left out the needs to 'patch/replace'
the
> > keyboard
>
> No, I didn't leave it out. Read the page.
Okay. My mistake. IMHO, this would be the greatest pain of all to go
thru...
-James Seng