Return-Path: Received: from murder ([unix socket]) by eikenes.alvestrand.no (Cyrus v2.2.8-Mandrake-RPM-2.2.8-4.2.101mdk) with LMTPA; Thu, 24 Mar 2005 16:00:50 +0100 X-Sieve: CMU Sieve 2.2 Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id C885861B4C for ; Thu, 24 Mar 2005 16:00:50 +0100 (CET) Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31593-07 for ; Thu, 24 Mar 2005 16:00:48 +0100 (CET) Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by eikenes.alvestrand.no (Postfix) with ESMTP id 2C59361B49 for ; Thu, 24 Mar 2005 16:00:48 +0100 (CET) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DETlU-0001pU-Dd; Thu, 24 Mar 2005 09:56:52 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DETlS-0001ow-CJ for ltru@megatron.ietf.org; Thu, 24 Mar 2005 09:56:50 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18716 for ; Thu, 24 Mar 2005 09:56:48 -0500 (EST) Received: from [63.247.76.194] (helo=montage.altserver.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DETr8-0005v9-JO for ltru@ietf.org; Thu, 24 Mar 2005 10:02:43 -0500 Received: from lns-p19-19-idf-82-65-128-79.adsl.proxad.net ([82.65.128.79] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1DETlO-0002B2-SB; Thu, 24 Mar 2005 06:56:47 -0800 Message-Id: <6.1.2.0.2.20050324145501.040b4eb0@mail.jefsey.com> X-Sender: jefsey+jefsey.com@mail.jefsey.com X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Thu, 24 Mar 2005 15:25:12 +0100 To: "Addison Phillips" , From: "JFC (Jefsey) Morfin" Subject: RE: [Ltru] Re: Registry in record-jar format In-Reply-To: <634978A7DF025A40BFEF33EB191E13BC0AB82E84@irvmbxw01.quest.c om> References: <634978A7DF025A40BFEF33EB191E13BC0AB82E84@irvmbxw01.quest.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - montage.altserver.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - jefsey.com X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Cc: X-BeenThere: ltru@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Language Tag Registry Update working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ltru-bounces@lists.ietf.org Errors-To: ltru-bounces@lists.ietf.org X-Virus-Scanned: amavisd-new at alvestrand.no At 14:32 24/03/2005, Addison Phillips wrote: >The question about lots of non-ASCII (JFC's comment) is a spurious one: by >rule it should be limited to the name of the described language or >language part in that language or to descriptive fields (both >informative). The normative data would still be restricted to ASCII. I am always happy to read constructive comments. Obviously ASCII fits the ASCII Internet. The question is will it fit the Multilingual Internet we all work on? I am just interested to know if what you consider spurious is "non-ASCII" or "lots". And if you think user's descriptive fields MUST or SHOULD be in ASCII (obviously only a MUST would go your way). Also, when you speak of normative data, do you speak of normative codes and numbers or of all the data in the norm, i.e. including French texts, (and happily sometimes, for the language norms Chinese, Russian, Arabic, etc. will be supported - again only a question of budget and international agreements we do not control)? ASCII will not even fully support French which is a normative language. jfc _______________________________________________ Ltru mailing list Ltru@lists.ietf.org https://www1.ietf.org/mailman/listinfo/ltru