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; Fri, 08 Apr 2005 17:46:35 +0200 X-Sieve: CMU Sieve 2.2 Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 6A98461B5E for ; Fri, 8 Apr 2005 17:46:35 +0200 (CEST) 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 08449-08 for ; Fri, 8 Apr 2005 17:46:31 +0200 (CEST) Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by eikenes.alvestrand.no (Postfix) with ESMTP id 43FA061B05 for ; Fri, 8 Apr 2005 17:46:31 +0200 (CEST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJveE-0003IS-8a; Fri, 08 Apr 2005 11:43:54 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJveC-0003II-FX for ltru@megatron.ietf.org; Fri, 08 Apr 2005 11:43:52 -0400 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 LAA04555 for ; Fri, 8 Apr 2005 11:43:50 -0400 (EDT) Received: from [63.247.76.195] (helo=montage.altserver.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJvmy-0004IK-6u for ltru@ietf.org; Fri, 08 Apr 2005 11:52:57 -0400 Received: from lns-p19-2-idf-82-251-152-231.adsl.proxad.net ([82.251.152.231] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1DJvdi-0002k3-PN; Fri, 08 Apr 2005 08:43:23 -0700 Message-Id: <6.1.2.0.2.20050408103302.03adfbc0@mail.jefsey.com> X-Sender: jefsey+jefsey.com@mail.jefsey.com X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Fri, 08 Apr 2005 17:43:06 +0200 To: ltru@ietf.org From: "JFC (Jefsey) Morfin" Subject: Re: [Ltru] registry should be bilingual In-Reply-To: References: 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 - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - jefsey.com X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002 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 On 03:11 08/04/2005, rt+ltru-registry@rt.psg.com said: >Hi - >(co-chair hat ON) > >The question of adding French translations of specific fields in the registry >was raised in http://www1.ietf.org/mail-archive/web/ltru/current/msg00094.html > >Though this was discussed at some length on the ietf-languages list, I'd >like to >verify that we have a rough consensus in this WG. I believe that consensus is >to reject this proposal. Please speak up if you have compelling technical >arguments >that this WG should add French translations of specific fields in the >registry. (Various hats ON) I am surprised by this. I will only repeat my position expressed often on the IETF main list and to this IETF WG-ltru: French and English are equally compelling for the IANA language tags registry, for reasons which should be obvious for standadizers of a global system. Among these reasons: - this is the rule of the ISO standards considered by the Charter. Additions to these standards are to be homogenous with these standards. - they make sure that at least experts from two major visions were involved: a protection of the interests and rights of every other culture. - this is a necessary technical seed for the support of multilingualism over internationalisation. ISO biculturalism is a first step to what should extend to other languages like Spanish, Russian, Chinese and Arabic and, further on to every languages, as required by a Multilingual Internet. The error of RFC 3066 in that area MUST not be repeated. I measure the technical complexity of the Multilingual Internet, the IAB avoided to consider among its RFC 3869's R&D priorities. But I think that to leave its architectural organization to a grassroots process is inappropriate. Langtags are by essence the basic building blocks of this evolution. They must be standardized as such. The lack of lingual consistency between BCP 047 and ISO standards would therefore prevent any consensus. A lack of consideration of multilingualism can only to a Internet balkanization we do not want. J-F C. Morfin _______________________________________________ Ltru mailing list Ltru@lists.ietf.org https://www1.ietf.org/mailman/listinfo/ltru