[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] Fast nameprep vs. slow nameprep
- To: "Dan Ebert" <dan@enic.cc>, "Keith Moore" <moore@cs.utk.edu>
- Subject: Re: [idn] Fast nameprep vs. slow nameprep
- From: "James Seng/Personal" <James@Seng.cc>
- Date: Fri, 2 Feb 2001 10:16:30 +0800
- Cc: <idn@ops.ietf.org>
- Delivery-date: Thu, 01 Feb 2001 18:18:16 -0800
- Envelope-to: idn-data@psg.com
I suggest reading the I-D IDNA (or IDNRA) draft. This issue has been
discussed in the I-D.
-James Seng
----- Original Message -----
From: "Dan Ebert" <dan@enic.cc>
To: "Keith Moore" <moore@cs.utk.edu>
Cc: <idn@ops.ietf.org>
Sent: Friday, February 02, 2001 9:40 AM
Subject: Re: [idn] Fast nameprep vs. slow nameprep
> Keith Moore wrote:
> >
> > note that in the case of your scenario B - a URL within a web page
> > will be in the document character set, which might or might not be
> > UTF-8. so it might also need translation in addition to nameprep
> > and ACE.
>
> It seems to me that there would also be a possible (probable?) need
for
> translation from an OS character set (Big 5, GB 2312, ISO8859-x, etc.)
> to UTF-8 (and to ACE?) when a user types a multilingual domainname
into
> a browser's location bar.
>
> --
> Dan Ebert dan@enic.cc eNIC Corporation
>