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; Wed, 15 Jun 2005 03:09:47 +0200 X-Sieve: CMU Sieve 2.2 Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id BD50961B4B for ; Wed, 15 Jun 2005 03:09:47 +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 07839-03 for ; Wed, 15 Jun 2005 03:09:44 +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 18C6661B07 for ; Wed, 15 Jun 2005 03:09:44 +0200 (CEST) Received: from ver78-2-82-241-91-24.fbx.proxad.net ([82.241.91.24] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1DiMPT-0001i5-0T; Tue, 14 Jun 2005 18:09:39 -0700 Message-Id: <6.2.1.2.2.20050615020342.0386ae50@mail.jefsey.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Wed, 15 Jun 2005 02:58:58 +0200 To: Karen_Broome@spe.sony.com, Harald Tveit Alvestrand From: "JFC (Jefsey) Morfin" Subject: RE: Swiss german, spoken Cc: 'IETF Languages Discussion' , Debbie Garside 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 - 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 At 01:48 15/06/2005, Karen_Broome@spe.sony.com wrote: >Well-formed XML uses the xml:lang attribute to specify the content >language, not a tag, though that would work in an informal use. >I was speaking of the formal use for which RFC 3066 is prescribed. Dear Karen, I am afraid you are discussing a gray area. The Internet content comes from text. All the issues discussed here are text related. Obviously today text is only part of language support and the ecosystem is multilingual, multimedia, multimode, multitechnology, multi-etc. I say that this Registry is able to answer that need. This is not the way this list sees its own charter and not the charter of the WG-ltru, which are to add script only, meaning restricting RFC 3066 to only one medium. This is not our only need: we need to stay fully in tune with the ISO standards which want to be multilingual, multimedia, multimode, multitechnology and with the ISO registry scheme for scalability and conflict containment. This is why we will build a consistent extended Language Identidication Scheme in using x-tags. Outside of the IANA registry to comply with the ICANN experimentation criteria (ICP-3) we adhere to. This mailing list is the only one I know to discuss RFC 3066 applications, So, I will continue documenting this project in here, since http://rfc3066.org would mean a kind of split/balkanisation, none wants to risk. jfc