LANGUAGE SUBTAG REGISTRATION FORM (R4) - Pinyin
addison at amazon.com
Fri Sep 26 17:09:33 CEST 2008
Gosh, should we start the argument about whether the year goes first or last now?
I totally prefer 1958hpin. Or, given what we’re identifying, maybe it should be sort of “tone-mark-like”: h1p9i5n8.
Globalization Architect -- Lab126
Internationalization is not a feature.
It is an architecture.
From: ietf-languages-bounces at alvestrand.no [mailto:ietf-languages-bounces at alvestrand.no] On Behalf Of Mark Davis
Sent: Friday, September 26, 2008 4:41 AM
To: Tracey, Niall
Cc: Randy Presuhn; ietf-languages at iana.org
Subject: LANGUAGE SUBTAG REGISTRATION FORM (R4) - Pinyin
I've produced a modified version of my R3, with the following changes:
- change of the subtag name for consistency with Michael's approach on Belerusian
- addition of zh-Latn prefix (as discussed on the list)
- some additional information on the letters used in this system.
LANGUAGE SUBTAG REGISTRATION FORM (R4)
1. Name of requester:
2. E-mail address of requester:
markdavis at google.com<mailto:markdavis at google.com>
3. Record Requested:
Description: Hanyu Pinyin romanization of Mandarin Chinese
4. Intended meaning of the subtag:
To distinguish Mandarin Chinese content written in Latin characters using the Hanyu Pinyin romanization (as adopted by China in 1958) from the other possible transcriptions. It uses the Latin letters [aáàǎā b-d eéèěē f-h iíìǐī j-n oóòǒō p-t uúùǔū üǘǜǚǖ w-z]: that is, a-z, minus v, plus ü and 4 additional accented versions of each of the vowels.
5. Reference to published description of the language (book or article):
Hanyu Pinyin, the most commonly used system for Mandarin Chinese romanization, has been the national standard of China since 1958, and an international standard (ISO 7098:1991, 2nd ed.) since 1982.
See also the LOC page for the relation between Hanyu Pinyin and Wade-Giles: http://www.loc.gov/catdir/pinyin/romcover.html
6. Any other relevant information:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ietf-languages