RFC 2482 on Language Tagging in Unicode Plain Text
RFC Editor <rfc-ed@ISI.EDU> Thu, 14 January 1999 01:35 UTC
Received: (from adm@localhost) by ietf.org (8.8.5/8.8.7a) id UAA22492 for ietf-123-outbound.10@ietf.org; Wed, 13 Jan 1999 20:35:02 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.8.5/8.8.7a) with ESMTP id UAA22328 for <all-ietf@ietf.org>; Wed, 13 Jan 1999 20:24:08 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id RAA00658; Wed, 13 Jan 1999 17:24:09 -0800 (PST)
Message-Id: <199901140124.RAA00658@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2482 on Language Tagging in Unicode Plain Text
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 13 Jan 1999 17:24:09 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2482: Title: Language Tagging in Unicode Plain Text Author(s): K. Whistler, G. Adams Status: Informational Date: January 1999 Mailbox: kenw@sybase.com, glenn@spyglass.com Pages: 14 Characters: 27800 Updates/Obsoletes/See Also: None I-D Tag: draft-whistler-plane14-00.txt URL: ftp://ftp.isi.edu/in-notes/rfc2482.txt This document proposed a mechanism for language tagging in [UNICODE] plain text. A set of special-use tag characters on Plane 14 of [ISO10646] (accessible through UTF-8, UTF-16, and UCS-4 encoding forms) are proposed for encoding to enable the spelling out of ASCII-based string tags using characters which can be strictly separated from ordinary text content characters in ISO10646 (or UNICODE). This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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.echo 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 Alegre Ramos USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.