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:39:19 +0200 X-Sieve: CMU Sieve 2.2 Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 01A7D61B67 for ; Sun, 10 Apr 2005 01:39:18 +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 28932-08 for ; Sun, 10 Apr 2005 01:39:15 +0200 (CEST) Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by eikenes.alvestrand.no (Postfix) with ESMTP id E047B61B50 for ; Sun, 10 Apr 2005 01:39:14 +0200 (CEST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DKPUR-0004XR-0j; Sat, 09 Apr 2005 19:35:47 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DKPUP-0004XM-04 for ltru@megatron.ietf.org; Sat, 09 Apr 2005 19:35:45 -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 TAA17406 for ; Sat, 9 Apr 2005 19:35:42 -0400 (EDT) Received: from [63.247.76.195] (helo=montage.altserver.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DKPdS-0003DG-Qv for ltru@ietf.org; Sat, 09 Apr 2005 19:45:07 -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 1DKPU3-0007eU-64; Sat, 09 Apr 2005 16:35:23 -0700 Message-Id: <6.1.2.0.2.20050410005620.03ce5c40@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:01:26 +0200 To: Misha Wolf , LTRU Working Group From: "JFC (Jefsey) Morfin" Subject: RE: [Ltru] Compatibility with existing use (LDAP) In-Reply-To: <1987416CA83AC7499AC772F92E2DBF78037C9AFC@LONSMSXM02.emea.i me.reuters.com> References: <1987416CA83AC7499AC772F92E2DBF78037C9AFC@LONSMSXM02.emea.ime.reuters.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 - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - jefsey.com X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88 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 Misha, I think you should be clearer. With real ISO 3166 codes. What you really discuss is for an LDAP meta-database on Chinese speaking web sites to enter: zh-Hant-tw or zh-tw-Hant zh-Hant-cn or zn-cn-Hant zh-Hant-sg or zn-sh-Hant etc... ? And CN people to querry that database?? jfc At 23:05 09/04/2005, Misha Wolf wrote: >Ira McDonald wrote: > > > If script tags SHOULD be rare in use, then it's no burden for > > them to occupy the third position, rather than the second. > >I cannot imagine what mental model you have of *why* a >script or a country should be included in a language tag. > >Consider "zh". And consider the *very* large number of >people wanting to tag their text as, or look for text in, >either Traditional or Simplified Chinese. Are you serious >in arguing that they should have to inject a country code >between "zh" and the "Hant" or "Hans"? > >Let's see: The person requesting a resource will have to >specify a list of languages, of the form zh-C1-Hant, >zh-C2-Hant, zh-C3-Hant, in order to obtain all resources in >Traditional Chinese. > >And what do you expect the person tagging a resource to do? >In general, they don't have the possibility of using multiple >tags (zh-C1-Hant, zh-C2-Hant, zh-C3-Hant) to describe their >resource. So what should they do? If they choose just one, >eg zh-C2-Hant, then requestors specifying either zh-C1-Hant >or zh-C3-Hant will not get the resource. > >I feel that those who advocate the ll-CC-Scipt approach are >simply sticking their heads in the sand and refusing to >engage with reality. > > > Semi-OT - the inclusion of script tags in language tags breaks > > utterly the utility of presenting language choices to users in > > GUIs as country-flag icons - the script differences would be > > invisible. > >I can't imagine how you can seek to portray something so >daft as being a reasonable practice. > >Misha > > > > >----------------------------------------------------------------- > Visit our Internet site at http://www.reuters.com > >To find out more about Reuters Products and Services visit >http://www.reuters.com/productinfo > >Any views expressed in this message are those of the individual >sender, except where the sender specifically states them to be >the views of Reuters Ltd. > > >_______________________________________________ >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