[Ltru] Fw: BCP0047 RFC 4646 on Tags for Identifying Languages
"Randy Presuhn" <randy_presuhn@mindspring.com> Fri, 08 September 2006 23:07 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GLpRW-0002oM-19; Fri, 08 Sep 2006 19:07:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GLpRU-0002oG-IO for ltru@ietf.org; Fri, 08 Sep 2006 19:07:24 -0400
Received: from elasmtp-kukur.atl.sa.earthlink.net ([209.86.89.65]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GLpRT-0005R3-4u for ltru@ietf.org; Fri, 08 Sep 2006 19:07:24 -0400
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=n/+5+yMhelsNskIvN6me9Brzevot+18QGsefPl7cAAwUwQQiqUuAwvkmleDc6toA; h=Received:Message-ID:From:To:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [68.165.3.121] (helo=oemcomputer) by elasmtp-kukur.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1GLpRO-0000Dz-5R for ltru@ietf.org; Fri, 08 Sep 2006 19:07:18 -0400
Message-ID: <001b01c6d39b$fce81e60$6501a8c0@oemcomputer>
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: LTRU Working Group <ltru@ietf.org>
Date: Fri, 08 Sep 2006 16:10:33 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888866e14058d4cf7af59362e258c7ad8696982c6326ee2a776350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 68.165.3.121
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Subject: [Ltru] Fw: BCP0047 RFC 4646 on Tags for Identifying Languages
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
Errors-To: ltru-bounces@ietf.org
Hi - Congratulations to all concerned! Randy, ltru co-chair ----- Original Message ----- > From: <rfc-editor@rfc-editor.org> > To: <ietf-announce@ietf.org>; <rfc-dist@rfc-editor.org> > Cc: <rfc-editor@rfc-editor.org> > Sent: Friday, September 08, 2006 3:44 PM > Subject: BCP0047 RFC 4646 on Tags for Identifying Languages > > > A new Request for Comments is now available in online RFC libraries. > > BCP0047 > RFC 4646 > > Title: Tags for Identifying Languages > Author: A. Phillips, M. Davis > Status: Best Current Practice > Date: September 2006 > Mailbox: addison@inter-locale.com, > mark.davis@macchiato.com > Pages: 59 > Characters: 135810 > > > I-D Tag: draft-ietf-ltru-registry-14.txt > > URL: http://www.rfc-editor.org/rfc/rfc4646.txt > > This document describes the structure, content, construction, and > semantics of language tags for use in cases where it is desirable to > indicate the language used in an information object. It also > describes how to register values for use in language tags and the > creation of user-defined extensions for private interchange. This > document, in combination with RFC 4647, replaces RFC 3066, which > replaced RFC 1766. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. > > This document is a product of the Language Tag Registry Update > Working Group of the IETF > > This document specifies an Internet Best Current Practices for the > Internet Community, and requests discussion and suggestions for > improvements. Distribution of this memo is unlimited. > > This announcement is sent to the IETF list and the RFC-DIST list. > Requests to be added to or deleted from the IETF distribution list > should be sent to IETF-REQUEST@IETF.ORG. Requests to be > added to or deleted from the RFC-DIST distribution list should > be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. > > Details on obtaining RFCs via FTP or EMAIL may be obtained by sending > an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body > > help: ways_to_get_rfcs. For example: > > To: rfc-info@RFC-EDITOR.ORG > Subject: getting rfcs > > help: ways_to_get_rfcs > > Requests for special distribution should be addressed to either the > author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. > > Submissions for Requests for Comments should be sent to > RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC > Authors, for further information. > > > Joyce K. Reynolds and Sandy Ginoza > USC/Information Sciences Institute > > ... > > > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ Ltru mailing list Ltru@ietf.org https://www1.ietf.org/mailman/listinfo/ltru
- [Ltru] Fw: BCP0047 RFC 4646 on Tags for Identifyi… Randy Presuhn