[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] Thoughts on nameprep
- To: "D. J. Bernstein" <djb@cr.yp.to>, <idn@ops.ietf.org>
- Subject: Re: [idn] Thoughts on nameprep
- From: "James Seng/Personal" <James@Seng.cc>
- Date: Sun, 11 Mar 2001 20:37:04 +0800
- Delivery-date: Sun, 11 Mar 2001 04:41:48 -0800
- Envelope-to: idn-data@psg.com
Dan,
> But Bruce, writing from Japan, says that the answer is no. Users type
> full-width kana. Redeploying network software to convert half-width
kana
> to full-width kana, as Patrik is insisting that we do, would be
idiotic.
You are basing your argument on a single non-Japanese based in Japan to
make an assumption that Japanese cannot key in half-width kana?
Why not lets hear it out from the Japanese who is on this working group.
I would appreciate if Yoneya-san could step forward to clarify the
situation.
> Tables that aren't in current software. Tables that may change. We're
> talking about software upgrades on a massive scale, and perhaps
further
> upgrades on the same scale when Unicode is modified. I'm astounded
that
> some people are taking such a careless approach to such a large
project.
Transcoding between legacy and Unicode is a large table. Transcoding may
change as standard evolves. However, that does not seem to prevent
people from using legacy encodings and UTF-8 interexchangely within
applications.
Table is not an issue. Making these tables up-to-date and freely
available is the concern.
> Registrars will forbid strings that have an e followed by a combining
> acute accent. They'll allow the precomposed e-with-acute-accent.
And you assumed only Registrars will put names into DNS entries? I have
not realised that DNS has evolved to a stage where it become a property
of Registries and Registrars only.
> If there is a problem, why not fix it in the keyboard interface for
that
> locale? This is fast nameprep: bad names are converted to good names
> before they escape the keyboard interface.
Why do you think people is going to fit their keyboard for just IDN?
Lets see if I can follow the logic.
We want IDN. We want IDN to do UTF-8 and we want easy way (fast
nameprep). Since some keyboard does not do it 'correctly' aka 'the way
we want it', let's fix all keyboard.
Please explain to me how you going to tell keyboard people that you want
them to change something which has been working all the time to fix a
problem in IDN?
-James Seng