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; Sun, 10 Apr 2005 01:38:16 +0200 X-Sieve: CMU Sieve 2.2 Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 2DDA261B62 for ; Sun, 10 Apr 2005 01:38:16 +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 28846-09 for ; Sun, 10 Apr 2005 01:38:13 +0200 (CEST) Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by eikenes.alvestrand.no (Postfix) with ESMTP id 594A061B50 for ; Sun, 10 Apr 2005 01:38:13 +0200 (CEST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DKPUs-0004ZE-8I; Sat, 09 Apr 2005 19:36:14 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DKPUm-0004YM-N5 for ltru@megatron.ietf.org; Sat, 09 Apr 2005 19:36:08 -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 TAA17463 for ; Sat, 9 Apr 2005 19:36:05 -0400 (EDT) Received: from [63.247.76.195] (helo=montage.altserver.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DKPdq-0003Jc-Hh for ltru@ietf.org; Sat, 09 Apr 2005 19:45:30 -0400 Received: from lns-p19-8-idf-82-249-30-81.adsl.proxad.net ([82.249.30.81] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1DKPU7-0007eU-2H; Sat, 09 Apr 2005 16:35:27 -0700 Message-Id: <6.1.2.0.2.20050410012624.03b19ce0@mail.jefsey.com> X-Sender: jefsey+jefsey.com@mail.jefsey.com X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Sun, 10 Apr 2005 01:33:55 +0200 To: "Randy Presuhn" , "LTRU Working Group" From: "JFC (Jefsey) Morfin" Subject: Re: [Ltru] Compatibility with existing use (LDAP) In-Reply-To: <001601c53d4e$6a5ab4c0$7f1afea9@oemcomputer> References: <1987416CA83AC7499AC772F92E2DBF78037C9AFC@LONSMSXM02.emea.ime.reuters.com> <001601c53d4e$6a5ab4c0$7f1afea9@oemcomputer> 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: 4d87d2aa806f79fed918a62e834505ca 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 Dear Randy, what you propose here has a name: flexibility. And flexibility is a requirement for scalability. Why I disagree with the initial approach of this WG is because we did not start in considering the Charter, what it wanted and what it permited to discuss to provide the best and most generalized response. I think that what you suggest is exactly what the Charter should lead us to. 1. to help users to use ISO standards and any other one or private proposition they may have to best understand each others 2. to propose a framework for every alternative - including APMD format - to be precisely documented, adequately supported, used as required and fully understood. Cheers! jfc At 23:52 09/04/2005, Randy Presuhn wrote: >Hi - > >As a technical contributor, the longer this thread goes on >the more consideration I think we should give to alternatives like >http://www.ietf.org/internet-drafts/draft-lilly-content-script-01.txt > >If we were to treat the identification of the language(variant), >the script, and the orthography of a text as three distinct >attributes, rather than trying to structure them into a single string >called a "language tag" would it ultimately make things simpler >or more complicated? > >I find this approach intuitively appealing in the case where there are >multiple orthographic alternatives in the same script for a >given language, yet it has no impact at all on texts in languages >where identification of the script or orthography in use is of >no particular interest. Even transcriptions and transliterations can >be handled nicely into this kind of approach, since they just become >orthographic alternatives. > >It would, however, require a re-thinking of how we've handled >German and Chinese. > >Randy > > > > >_______________________________________________ >Ltru mailing list >Ltru@lists.ietf.org >https://www1.ietf.org/mailman/listinfo/ltru _______________________________________________ Ltru mailing list Ltru@lists.ietf.org https://www1.ietf.org/mailman/listinfo/ltru