[Ltru] Non-Latin-1 Description fields in RFC 4645bis
"Doug Ewell" <dewell@roadrunner.com> Thu, 06 December 2007 15:42 UTC
Return-path: <ltru-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J0IsK-0001xr-44; Thu, 06 Dec 2007 10:42:56 -0500
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1J0IsI-0001xj-JE for ltru-confirm+ok@megatron.ietf.org; Thu, 06 Dec 2007 10:42:54 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J0IsI-0001xb-8G for ltru@ietf.org; Thu, 06 Dec 2007 10:42:54 -0500
Received: from mta11.adelphia.net ([68.168.78.205]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J0IsH-0005sB-Ny for ltru@ietf.org; Thu, 06 Dec 2007 10:42:54 -0500
Received: from DGBP7M81 ([76.167.184.182]) by mta11.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with SMTP id <20071206154253.BMKK19654.mta11.adelphia.net@DGBP7M81> for <ltru@ietf.org>; Thu, 6 Dec 2007 10:42:53 -0500
Message-ID: <019801c8381e$aa177ee0$6601a8c0@DGBP7M81>
From: Doug Ewell <dewell@roadrunner.com>
To: LTRU Working Group <ltru@ietf.org>
References: <E1Izxc3-0006VO-HS@megatron.ietf.org>
Date: Thu, 06 Dec 2007 07:42:52 -0800
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"; reply-type="original"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433
Subject: [Ltru] Non-Latin-1 Description fields in RFC 4645bis
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
Here are the Description fields in the proposed RFC 4645bis Registry that contain non-Latin-1 characters. This is presented in blocks showing the type and value of the subtag, as well as the non-Latin-1 description, so readers can look up the full context in draft-4645bis-02 (or -03, when it's ready). There are two blocks of listings here. The first is in hex NCRs, as they will appear in RFC 4645bis. This is shown here for the benefit of WG members who cannot see non-Latin-1 characters in their e-mail or on the Web-based mailing list archive. The second block is in UTF-8. Not all of these Description fields are the sole Description field for their respective subtag. For example, the script subtag 'Ethi' also has the description "Ethiopic", so technically it doesn't matter for this discussion whether the string "Geʻez" is "Latin-script" or not; the subtag already has a "Latin-script" description as required. However, all of the non-Latin-1 Description fields are shown here, to help us make a well-informed decision. RFC 4646bis says, "At least one of the 'Description' fields MUST be written or transcribed into the Latin script." It does not say every character in that field must have the word LATIN in its Unicode name, must have the "Latn" script property in Unicode, must be present in Latin-1, Windows-1252, MES-1, etc. As Frank points out, we don't have an operational definition of "Latin script" to guide us here. All of the characters in these Description fields do have either the "Latn" or "Zyyy" (Common) script property in Unicode, and all belong to one of the following Unicode blocks: * Basic Latin * Latin-1 Supplement * Latin Extended-A * Spacing Modifier Letters * Latin Extended Additional * General Punctuation ----- Hex NCRs: Type: language Subtag: gwi Description: Gwichʼin Type: language Subtag: nqo Description: N’Ko Type: language Subtag: pka Description: Ardhamāgadhī Prākrit Description: Prākrit, Ardhamāgadhī Type: language Subtag: pmh Description: Māhārāṣṭri Prākrit Description: Prākrit, Māhārāṣṭri Type: language Subtag: psu Description: Sauraseni Prākrit Description: Prākrit, Sauraseni Type: script Subtag: Ethi Description: Geʻez Type: script Subtag: Hang Description: Hangŭl Type: script Subtag: Nkoo Description: N’Ko ----- UTF-8: Type: language Subtag: gwi Description: Gwichʼin Type: language Subtag: nqo Description: N’Ko Type: language Subtag: pka Description: Ardhamāgadhī Prākrit Description: Prākrit, Ardhamāgadhī Type: language Subtag: pmh Description: Māhārāṣṭri Prākrit Description: Prākrit, Māhārāṣṭri Type: language Subtag: psu Description: Sauraseni Prākrit Description: Prākrit, Sauraseni Type: script Subtag: Ethi Description: Geʻez Type: script Subtag: Hang Description: Hangŭl Type: script Subtag: Nkoo Description: N’Ko -- Doug Ewell * Fullerton, California, USA * RFC 4645 * UTN #14 http://home.roadrunner.com/~dewell http://www1.ietf.org/html.charters/ltru-charter.html http://www.alvestrand.no/mailman/listinfo/ietf-languages ˆ _______________________________________________ Ltru mailing list Ltru@ietf.org https://www1.ietf.org/mailman/listinfo/ltru
- [Ltru] Non-Latin-1 Description fields in RFC 4645… Doug Ewell
- Re: [Ltru] Non-Latin-1 Description fields in RFC … John Cowan
- Re: [Ltru] Non-Latin-1 Description fields in RFC … Doug Ewell
- [Ltru] Re: Non-Latin-1 Description fields in RFC … Frank Ellermann
- [Ltru] Re: Non-Latin-1 Description fields in RFC … Doug Ewell
- [Ltru] Re: Non-Latin-1 Description fields in RFC … Frank Ellermann
- [Ltru] Re: Non-Latin-1 Description fields in RFC … Doug Ewell
- Re: [Ltru] Re: Non-Latin-1 Description fields in … Mark Davis
- Re: [Ltru] Re: Non-Latin-1 Description fields in … Addison Phillips
- Re: [Ltru] Re: Non-Latin-1 Description fields in … Doug Ewell
- [Ltru] Re: Non-Latin-1 Description fields in RFC … Frank Ellermann