IETF Logo Mail Archive

Re: [idn] Re: character tables

Erik van der Poel <erik@vanderpoel.org> Mon, 28 February 2005 04:25 UTC

Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07308 for <idn-archive@lists.ietf.org>; Sun, 27 Feb 2005 23:25:24 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.44 (FreeBSD)) id 1D5cNQ-000Otc-90 for idn-data@psg.com; Mon, 28 Feb 2005 04:19:24 +0000
Received: from [207.115.63.77] (helo=pimout1-ext.prodigy.net) by psg.com with esmtp (Exim 4.44 (FreeBSD)) id 1D5cNN-000OtK-59 for idn@ops.ietf.org; Mon, 28 Feb 2005 04:19:21 +0000
Received: from [10.1.1.2] (adsl-64-174-147-206.dsl.sntc01.pacbell.net [64.174.147.206]) by pimout1-ext.prodigy.net (8.12.10 milter /8.12.10) with ESMTP id j1S4J9SJ246782; Sun, 27 Feb 2005 23:19:14 -0500
Message-ID: <42229BBC.8020608@vanderpoel.org>
Date: Sun, 27 Feb 2005 20:19:08 -0800
From: Erik van der Poel <erik@vanderpoel.org>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: John C Klensin <klensin@jck.com>
CC: idn@ops.ietf.org
Subject: Re: [idn] Re: character tables
References: <421B8484.3070802@vanderpoel.org> <20050223072837.GA21463~@nicemice.net> <D872CCF059514053ECF8A198@scan.jck.com> <421D8411.9030006@vanderpoel.org> <p06210208be4390618c81@[192.168.0.101]> <421E0D0C.2000309@vanderpoel.org> <p06210202be43c3888991@[192.168.0.101]> <E07CE813AD23B2D95DA0C740@scan.jck.com> <421E30F2.1040408@vanderpoel.org> <0E7F74C71945B923C52211F3@scan.jck.com> <421EA0C9.1010500@vanderpoel.org> <00a401c51af3$7863aae0$030aa8c0@DEWELL> <A574CA1BE87BFDA3C2A1AC0E@scan.jck.com> <421FA55B.9000308@vanderpoel.org> <421FCBD7.8000805@vanderpoel.org> <42227EBF.9040703@vanderpoel.org> <45781B7428C6AA07C3B283BD@scan.jck.com>
In-Reply-To: <45781B7428C6AA07C3B283BD@scan.jck.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.0.1
Sender: owner-idn@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

John C Klensin wrote:
> 
> 	(i) ICANN is still assuming that this is a registry
> 	issue.  As such, if someone else starts guessing at what
> 	a registry is doing, we may get into trouble, especially
> 	since the tables may not show all of the relevant
> 	registry rules and restrictions.

Hmmm... GNU libidn already seems to be trying to use machine-readable 
tables. I had a look at the GNU libidn page:

http://www.gnu.org/software/libidn/

It has a copy of an expired Internet Draft by Paul Hoffman:

http://josefsson.org/cgi-bin/rfcmarkup?url=http://josefsson.org/cgi-bin/viewcvs.cgi/*checkout*/libidn/doc/specifications/draft-hoffman-idn-reg-02.txt

This draft seems to be talking about bundling and blocking, which your 
draft talks about too. What happened here? Did Paul decide to let his 
expire?

Anyway, my only reason for trying to get machine-readable tables was to 
figure out which Unicode character categories were being used. Another 
way to get this info is to simply ask the registries. Or, we can suggest 
a list of categories and see if they would be happy with a nameprep-bis 
that limits the characters to those categories.

Erik

v2.23.0 | Report a Bug | By Email