Return-Path: Received: from eikenes.alvestrand.no ([unix socket]) by eikenes.alvestrand.no (Cyrus v2.1.11-Mandrake-RPM-2.1.11-1mdk) with LMTP; Thu, 17 Mar 2005 18:53:58 +0100 X-Sieve: CMU Sieve 2.2 Return-Path: Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id EC26C621E7; Thu, 17 Mar 2005 18:53:57 +0100 (CET) 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 25513-02; Thu, 17 Mar 2005 18:53:57 +0100 (CET) Received: from eikenes.alvestrand.no (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 481C0621E8; Thu, 17 Mar 2005 18:53:53 +0100 (CET) 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 6E768621E6 for ; Thu, 17 Mar 2005 18:53:51 +0100 (CET) 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 25339-10 for ; Thu, 17 Mar 2005 18:53:49 +0100 (CET) Received: from pechora.icann.org (pechora.icann.org [192.0.34.35]) by eikenes.alvestrand.no (Postfix) with ESMTP id 8331B621DE for ; Thu, 17 Mar 2005 18:53:48 +0100 (CET) Received: from montage.altserver.com (montage.altserver.com [63.247.76.195] (may be forged)) by pechora.icann.org (8.11.6/8.11.6) with ESMTP id j2HHowp04054 for ; Thu, 17 Mar 2005 09:50:58 -0800 Received: from lns-p19-2-idf-82-251-145-54.adsl.proxad.net ([82.251.145.54] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1DBzBk-0000CG-9C; Thu, 17 Mar 2005 09:53:41 -0800 Message-Id: <6.1.2.0.2.20050317181157.03969b40@mail.jefsey.com> X-Sender: jefsey+jefsey.com@mail.jefsey.com X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Thu, 17 Mar 2005 18:53:37 +0100 To: "Doug Ewell" , From: "JFC (Jefsey) Morfin" In-Reply-To: <009d01c52b0e$1f8b8160$030aa8c0@DEWELL> References: <009d01c52b0e$1f8b8160$030aa8c0@DEWELL> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: 8bit 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 - iana.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - jefsey.com X-Source: X-Source-Args: X-Source-Dir: X-Virus-Scanned: by amavisd-new at alvestrand.no Cc: Subject: Re: Distinguishing Greek and Greek 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: by amavisd-new at alvestrand.no Dear Peter and Doug, I respond here because this obviously has to do with the way this list conducts its registration review. But I think it would be better suited to the WG? I do not copy it there because you are the authors. At 17:26 17/03/2005, Doug Ewell wrote: >Peter Constable wrote: >He's talking about 5 "descriptors," which I guess are supposed to map to >the 5 elements of the language tagging mechanism he envisions. Correct. But they are/this is more related to the 5 levels/points underlaying a multilingual internet (I am not sure they are layers, they just are necessary) - identification of the language (ISO 693 or the like) -> interrelation between people - we can talk - internationalization (what discusses RFC 3066 - ISO 15924) -> interoperation between machines - we can write - multinationalization (taking into account ISO 3166 or other geopolitical attribute) -> interculturization between communities - we can share same cultural references, the same meanings (for example, what may be missing in here). - multilingualization (semantic, grammar, dictionary, syntax, etc.) -> interintelligibility -> we can understand each other - vernacularization (procedures, styles, tools, etc.) -> interusability -> we can do something together >I didn't think any Microsoft product dealt with "style" or "authority" >attributes, nor in script except to the extent that is covered by >registered RFC 3066 tags. Name the reference/authority, etc. the way you want. Authoritative in its domain is an usual concept in the Internet culture. You can certainly find other words. This is what says a computer that when I write in French this is not Greek, or what make you sure that when I write in Provencal it is not Berrichon. I gave in my response to Peer how and where the Word system does that. - tools - languages : language, script, country (you can qualify even if you do not understand). - tools - options (preferences?) : dictionary, style (you need them to understand and write). Which system do you use? Does it support the same descriptors? This being said, I understand your remark about what I name the multilingualization level. You say English is not defined. I belong to a culture where definition is known and supported for 4 centuries. This makes me more aware of this point. Actually English, in a way is more defined than French. When we introduce a computer in a culture, we do in a few months, a few years, what Richelieu and France did a long ago and matured over centuries: we create an "Académie de cette Langue". What I object is that this Académie may belong to anyone else than to the people sharing that culture. And naming is already a way to own. As long as it is to qualify the culture it is OK because there is a need. When it comes to enter in its definition this is - IMHO - an intrusion. And I refuse to share in that kind of intrusion. To the contrary my approach is to say we are here to serve, help, educate so they can first share in this process, comment it and eventually conduct it for themselves. I note that three days ago this list had 2 Greeks. Now 3 and probably 4. Because Greek persons stepped in and documented _their_ own languages. This is the way it should happen for every language, the request should come from each Internet community. This is the spirit of the text of RFC 3066. I fully understand that people who want to sell to that communities would like to speed up the process. I do not think it is commercially advisable to by-pass their future customers in this process (as the reactions to the Google's annoucement show it). To the contrary they should help empowering the language and help their cultural, linguistic, political authorities through the registration process. For example, I fully agree with you that the name of the langtag registrant is not necessary. But I would suggest to remove it only when the registration is by an outsider. jfc _______________________________________________ Ietf-languages mailing list Ietf-languages@alvestrand.no http://www.alvestrand.no/mailman/listinfo/ietf-languages