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; Tue, 14 Jun 2005 00:36:39 +0200 X-Sieve: CMU Sieve 2.2 Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id B59B261B43; Tue, 14 Jun 2005 00:36:39 +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 10763-02; Tue, 14 Jun 2005 00:36:39 +0200 (CEST) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 73A4C61B51; Tue, 14 Jun 2005 00:36:33 +0200 (CEST) X-Original-To: ietf-languages@alvestrand.no Delivered-To: ietf-languages@alvestrand.no Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id EC2B061B4B for ; Tue, 14 Jun 2005 00:36:31 +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 10547-09 for ; Tue, 14 Jun 2005 00:36:29 +0200 (CEST) X-Greylist: from auto-whitelisted by SQLgrey-1.4.8 Received: from montage.altserver.com (montage.altserver.com [63.247.74.122]) by eikenes.alvestrand.no (Postfix) with ESMTP id 349A661B43 for ; Tue, 14 Jun 2005 00:36:29 +0200 (CEST) Received: from [62.35.167.26] (helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1DhxXA-0003cX-Kk; Mon, 13 Jun 2005 15:35:57 -0700 Message-Id: <6.2.1.2.2.20050613223124.044bbeb0@mail.jefsey.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Mon, 13 Jun 2005 23:37:42 +0200 To: "Addison Phillips" , "Peter Constable" From: "JFC (Jefsey) Morfin" In-Reply-To: <634978A7DF025A40BFEF33EB191E13BC0BBB8CF7@irvmbxw01.quest.c om> References: <634978A7DF025A40BFEF33EB191E13BC0BBB8CF7@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 - alvestrand.no X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - jefsey.com X-Source: X-Source-Args: X-Source-Dir: X-Virus-Scanned: amavisd-new at alvestrand.no Cc: ietf-languages@alvestrand.no Subject: RE: Swiss german, spoken X-BeenThere: ietf-languages@alvestrand.no X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Language tag discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ietf-languages-bounces@alvestrand.no Errors-To: ietf-languages-bounces@alvestrand.no X-Virus-Scanned: amavisd-new at alvestrand.no At 19:26 13/06/2005, Addison Phillips wrote: >There is a working group (LTRU): you have not deigned to work with it. >You have no solution or cannot demonstrate one, and, if you do, this is >not the place for it, LTRU is. Dear Addison, I will not comment about "you have not deigned" which burst roars of laugh in here. They repeated with your "you have no solution".... Good to have some fun sometimes on this list. I know you cherish your Draft but here we discuss how to permit users (in this case Karen) to register a langtag they can use today and relate to their own standard for the pictures they produce. Not next year/decade when ISO 639-3 and your Draft can be used. This can only be addressed today in using "i-" or "x-". I am happy with both: we are totally flexible as we use double indexing. The only difference is if there is a list consensus endorsed by the Chair (he is the reviewer) or not. The problem is registering "i-gsw" or "x-gsw" alone looks silly. This is not the case if we register all projected ISO 639-3 and ISO 639-5 in "i-xxx". We have no problem is deciding that: - not yet ISO 639-3 subtags belong to ISO 639-5. I think this does not violate the ISO 639-3 concept. And we will never have a -3/-5 conflict. - we will from now on enter ISO 639-5 as "i-" tags. If this is not agreeable to this list, I have no problem reverting to "x-". I will the publish a BCP documenting that we will use "x-0", "x-3", "x-5", "x-6" for experimentation. "x-0" will be our direct indexing, "x-1", "x-2" "x-3", "x-5", "x-6" will use the string code of the concrned ISO table. This will leave three characters or more to document all the menus Karen needs. RFC 3066 format provides data about geographic/lingual communities. We will use ISO 3166-2, UN.9 and the X.121/E.164, Linguasphere, etc. The fun is that "x-9" will stand this way for languages and "xp--" for IDNs. It makes a simple and consistent extended system. Fully operational in a few days. Question: canwe/I use "i/x--zzz" or is there any known unforesseen restriction? Any objection? All the best. jfc _______________________________________________ Ietf-languages mailing list Ietf-languages@alvestrand.no http://www.alvestrand.no/mailman/listinfo/ietf-languages