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, 13 Sep 2005 09:53:32 +0200 X-Sieve: CMU Sieve 2.2 Received: from localhost (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 6C482320097 for ; Tue, 13 Sep 2005 09:53:32 +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 12813-01 for ; Tue, 13 Sep 2005 09:53:25 +0200 (CEST) X-Greylist: domain auto-whitelisted by SQLgrey-1.4.8 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by eikenes.alvestrand.no (Postfix) with ESMTP id 628FE320096 for ; Tue, 13 Sep 2005 09:53:25 +0200 (CEST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EF5Xi-0002hY-7G; Tue, 13 Sep 2005 03:49:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EExlq-0006xw-EJ; Mon, 12 Sep 2005 19:31:30 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08575; Mon, 12 Sep 2005 19:31:27 -0400 (EDT) Received: from montage.altserver.com ([63.247.74.122]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EExq7-0001ES-8i; Mon, 12 Sep 2005 19:35:56 -0400 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 1EExlf-0001S3-Ep; Mon, 12 Sep 2005 16:31:19 -0700 Message-Id: <6.2.3.4.2.20050912204409.04c785c0@mail.afrac.org> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Mon, 12 Sep 2005 21:30:49 +0200 To: "Peter Constable" , From: "JFC (Jefsey) Morfin" Subject: Re: [Ltru] RE: RFC 3066 bis Libraries list 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 - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - jefsey.com X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d X-Mailman-Approved-At: Mon, 12 Sep 2005 23:18:27 -0400 Cc: ltru@ietf.org X-BeenThere: ltru@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@ietf.org Errors-To: ltru-bounces@ietf.org X-Virus-Scanned: by amavisd-new at alvestrand.no At 17:04 12/09/2005, Peter Constable wrote: > > From: JFC (Jefsey) Morfin [mailto:jefsey@jefsey.com] > > Dear Peter, > > whatever the way you want to say it, these libraries have now to meet > > new specs they had not to meet before. > >I cannot say whether every existing software library written to conform >to RFC 3066 *has to* meet new specs. Certainly there will some, perhaps >many, that would be benefit from revision to the new specs. Dear Peter, The target is end to end interoperability between users/processes of non-English language. Users of every library MUST know to which extent the library they use fits the job or not, which alternative they can use. They should have a verification procedure to check their libraries depending on what they want. They should know how their software behaves when analysing specific langtag. For example, _some_ documentation is given by http://library.n0i.net/programming/perl/ac_tive/lib/I18N/LangTags/List.html. It is not strictly complying with any of the RFCs, nor giving the source code. That kind of information is a minimum. >If that was your intent, it would have been clearer to me had you asked >people to identify libraries they feel should be revised if the new spec >is adopted. You think some should escape the check? I do not know. I was expecting from you, from the authors, from the members of the WG-ltru, the list of all the libraries you know (URLs). You say they cannot support the users needs I presented, neither my big initial request to support to additional subtags (referent and context) nor even to support RFC documented URI-tags (a hook of a dedicated library?) jfc _______________________________________________ Ltru mailing list Ltru@ietf.org https://www1.ietf.org/mailman/listinfo/ltru