This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work in progress.”
The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 19, 2009.
Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
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.
2. The Language Tag
2.1.1. Formatting of Language Tags
2.2. Language Subtag Sources and Interpretation
2.2.1. Primary Language Subtag
2.2.2. Extended Language Subtags
2.2.3. Script Subtag
2.2.4. Region Subtag
2.2.5. Variant Subtags
2.2.6. Extension Subtags
2.2.7. Private Use Subtags
2.2.8. Grandfathered and Redundant Registrations
2.2.9. Classes of Conformance
3. Registry Format and Maintenance
3.1. Format of the IANA Language Subtag Registry
3.1.1. File Format
3.1.2. Record and Field Definitions
3.1.3. Type Field
3.1.4. Subtag and Tag Fields
3.1.5. Description Field
3.1.6. Deprecated Field
3.1.7. Preferred-Value Field
3.1.8. Prefix Field
3.1.9. Suppress-Script Field
3.1.10. Macrolanguage Field
3.1.11. Scope Field
3.1.12. Comments Field
3.2. Language Subtag Reviewer
3.3. Maintenance of the Registry
3.4. Stability of IANA Registry Entries
3.5. Registration Procedure for Subtags
3.6. Possibilities for Registration
3.7. Extensions and the Extensions Registry
3.8. Update of the Language Subtag Registry
4. Formation and Processing of Language Tags
4.1. Choice of Language Tag
4.1.1. Tagging Encompassed Languages
4.1.2. Using Extended Language Subtags
4.2. Meaning of the Language Tag
4.3. Lists of Languages
4.4. Length Considerations
4.4.1. Working with Limited Buffer Sizes
4.4.2. Truncation of Language Tags
4.5. Canonicalization of Language Tags
4.6. Considerations for Private Use Subtags
5. IANA Considerations
5.1. Language Subtag Registry
5.2. Extensions Registry
6. Security Considerations
7. Character Set Considerations
8. Changes from RFC 4646
9.1. Normative References
9.2. Informative References
Appendix A. Acknowledgements
Appendix B. Examples of Language Tags (Informative)
Appendix C. Examples of Registration Forms
§ Authors' Addresses
Human beings on our planet have, past and present, used a number of languages. There are many reasons why one would want to identify the language used when presenting or requesting information.
The language of an information item or a user's language preferences often need to be identified so that appropriate processing can be applied. For example, the user's language preferences in a Web browser can be used to select Web pages appropriately. Language information can also be used to select among tools (such as dictionaries) to assist in the processing or understanding of content in different languages. Knowledge about the particular language used by some piece of information content might be useful or even required by some types of processing; for example, spell-checking, computer-synthesized speech, Braille transcription, or high-quality print renderings.
One means of indicating the language used is by labeling the information content with an identifier or "tag". These tags can also be used to specify the user's preferences when selecting information content, or for labeling additional attributes of content and associated resources.
Sometimes language tags are used to indicate additional language attributes of content. For example, indicating specific information about the dialect, writing system, or orthography used in a document or resource may enable the user to obtain information in a form that they can understand, or it can be important in processing or rendering the given content into an appropriate form or style.
This document specifies a particular identifier mechanism (the language tag) and a registration function for values to be used to form tags. It also defines a mechanism for private use values and future extension.
This document replaces [RFC4646] (Phillips, A. and M. Davis, “Tags for Identifying Languages,” September 2006.), which replaced [RFC3066] (Alvestrand, H., “Tags for the Identification of Languages,” January 2001.) and its predecessor [RFC1766] (Alvestrand, H., “Tags for the Identification of Languages,” March 1995.). For a list of changes in this document, see Section 8 (Changes from RFC 4646).
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119] (Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.).
Language tags are used to help identify languages, whether spoken, written, signed, or otherwise signaled, for the purpose of communication. This includes constructed and artificial languages, but excludes languages not intended primarily for human communication, such as programming languages.
A language tag is composed from a sequence of one or more "subtags", each of which refines or narrows the range of language identified by the overall tag. Subtags, in turn, are a sequence of alphanumeric characters (letters and digits), distinguished and separated from other subtags in a tag by a hyphen ("-", ABNF (Crocker, D. and P. Overell, “Augmented BNF for Syntax Specifications: ABNF,” January 2008.) [RFC5234] %x2D).
There are different types of subtag, each of which is distinguished by length, position in the tag, and content: each subtag's type can be recognized solely by these features. This makes it possible to extract and assign some semantic information to the subtags, even if the specific subtag values are not recognized. Thus, a language tag processor need not have a list of valid tags or subtags (that is, a copy of some version of the IANA Language Subtag Registry) in order to perform common searching and matching operations. The only exceptions to this ability to infer meaning from subtag structure are the grandfathered tags listed in the productions 'regular' and 'irregular' below. These tags were registered under [RFC3066] (Alvestrand, H., “Tags for the Identification of Languages,” January 2001.) and are a fixed list that can never change.
The syntax of the language tag in ABNF [RFC5234] (Crocker, D. and P. Overell, “Augmented BNF for Syntax Specifications: ABNF,” January 2008.) is:
Language-Tag = langtag ; normal language tags / privateuse ; private use tag / grandfathered ; grandfathered tags langtag = language ["-" script] ["-" region] *("-" variant) *("-" extension) ["-" privateuse] language = 2*3ALPHA ; shortest ISO 639 code ["-" extlang] ; sometimes followed by ; extended language subtags / 4ALPHA ; or reserved for future use / 5*8ALPHA ; or registered language subtag extlang = 3ALPHA ; selected ISO 639 codes *2("-" 3ALPHA) ; permanently reserved script = 4ALPHA ; ISO 15924 code region = 2ALPHA ; ISO 3166-1 code / 3DIGIT ; UN M.49 code variant = 5*8alphanum ; registered variants / (DIGIT 3alphanum) extension = singleton 1*("-" (2*8alphanum)) ; Single alphanumerics ; "x" reserved for private use singleton = DIGIT ; 0 - 9 / %x41-57 ; A - W / %x59-5A ; Y - Z / %x61-77 ; a - w / %x79-7A ; y - z privateuse = "x" 1*("-" (1*8alphanum)) grandfathered = irregular ; non-redundant tags registered / regular ; during the RFC 3066 era irregular = "en-GB-oed" ; irregular tags do not match / "i-ami" ; the 'langtag' production and / "i-bnn" ; would not otherwise be / "i-default" ; considered 'well-formed' / "i-enochian" ; These tags are all valid, / "i-hak" ; but most are deprecated / "i-klingon" ; in favor of more modern / "i-lux" ; subtags or subtag / "i-mingo" ; combination / "i-navajo" / "i-pwn" / "i-tao" / "i-tay" / "i-tsu" / "sgn-BE-FR" / "sgn-BE-NL" / "sgn-CH-DE" regular = "art-lojban" ; these tags match the 'langtag' / "cel-gaulish" ; production, but their subtags / "no-bok" ; are not extended language / "no-nyn" ; or variant subtags: their meaning / "zh-guoyu" ; is defined by their registration / "zh-hakka" ; and all of these are deprecated / "zh-min" ; in favor of a more modern / "zh-min-nan" ; subtag or sequence of subtags / "zh-xiang" alphanum = (ALPHA / DIGIT) ; letters and numbers
| Figure 1: Language Tag ABNF |
For examples of language tags, see Appendix B (Examples of Language Tags (Informative)).
All subtags have a maximum length of eight characters and whitespace is not permitted in a language tag. There is a subtlety in the ABNF production 'variant': a variant starting with a digit has a minimum length of four characters, while those starting with a letter have a minimum length of five characters.
Although [RFC5234] (Crocker, D. and P. Overell, “Augmented BNF for Syntax Specifications: ABNF,” January 2008.) refers to octets, the language tags described in this document are sequences of characters from the US-ASCII [ISO646] (International Organization for Standardization, “ISO/IEC 646:1991, Information technology -- ISO 7-bit coded character set for information interchange.,” 1991.) repertoire. Language tags MAY be used in documents and applications that use other encodings, so long as these encompass the relevant part of the US-ASCII repertoire. An example of this would be an XML document that uses the UTF-16LE [RFC2781] (Hoffman, P. and F. Yergeau, “UTF-16, an encoding of ISO 10646,” February 2000.) encoding of [Unicode] (Unicode Consortium, “The Unicode Consortium. The Unicode Standard, Version 5.0, (Boston, MA, Addison-Wesley, 2003. ISBN 0-321-49081-0),” January 2007.).
At all times, language tags and their subtags, including private-use and extensions, are to be treated as case insensitive: there exist conventions for the capitalization of some of the subtags, but these MUST NOT be taken to carry meaning.
Thus, the tag "mn-Cyrl-MN" is not distinct from "MN-cYRL-mn" or "mN-cYrL-Mn" (or any other combination), and each of these variations conveys the same meaning: Mongolian written in the Cyrillic script as used in Mongolia.
The ABNF syntax also does not distinguish between upper and lowercase: the uppercase US-ASCII letters in the range 'A' through 'Z' are always considered equivalent and mapped directly to their US-ASCII lowercase equivalents in the range 'a' through 'z'. So the tag "I-AMI" is considered equivalent to that value "i-ami" in the 'irregular' production.
Although case distinctions do not carry meaning in language tags, consistent formatting and presentation of language tags will aid users. The format of subtags in the registry is RECOMMENDED as the form to use in language tags. This format generally corresponds to the common conventions for the various ISO standards from which the subtags are derived.
These conventions include:
An implementation can reproduce this format without accessing the registry as follows: All subtags, including extension and private use subtags, use lowercase letters, with two exceptions: two-letter and four-letter subtags that neither appear at the start of the tag nor occur after singletons. Such two-letter subtags are all uppercase (as in the tags "en-CA-x-ca" or "sgn-BE-FR") and four-letter subtags are titlecase (as in the tag "az-Latn-x-latn").
Note: Case folding of ASCII letters in certain locales, unless carefully handled, sometimes produces non-ASCII character values. The Unicode Character Database file "SpecialCasing.txt" defines the specific cases that are known to cause problems with this. In particular, the letter 'i' (U+0069) in Turkish and Azerbaijani is uppercased to U+0130 (LATIN CAPITAL LETTER I WITH DOT ABOVE). Implementers SHOULD specify a locale-neutral casing operation to ensure that case folding of subtags does not produce this value, which is illegal in language tags. For example, if one were to uppercase the region subtag 'in' using Turkish locale rules, the sequence U+0130 U+004E would result instead of the expected 'IN'.
The namespace of language tags and their subtags is administered by the Internet Assigned Numbers Authority (IANA) [RFC2860] (Carpenter, B., Baker, F., and M. Roberts, “Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority,” June 2000.) according to the rules in Section 5 (IANA Considerations) of this document. The Language Subtag Registry maintained by IANA is the source for valid subtags: other standards referenced in this section provide the source material for that registry.
Terminology used in this document:
Language tags are designed so that each subtag type has unique length and content restrictions. These make identification of the subtag's type possible, even if the content of the subtag itself is unrecognized. This allows tags to be parsed and processed without reference to the latest version of the underlying standards or the IANA registry and makes the associated exception handling when parsing tags simpler.
Some of the subtags in the IANA registry do not come from an underlying standard. These can only appear in specific positions in a tag: they can only occur as primary language subtags or as variant subtags.
Sequences of private use and extension subtags MUST occur at the end of the sequence of subtags and MUST NOT be interspersed with subtags defined elsewhere in this document. These sequences are introduced by single-character subtags, which are reserved as follows:
The primary language subtag is the first subtag in a language tag and cannot be omitted, with two exceptions:
The following rules apply to the primary language subtag:
- "ISO 639-2:1998 - Codes for the representation of names of languages -- Part 2: Alpha-3 code - edition 1" [ISO639‑2] (International Organization for Standardization, “ISO 639-2:1998. Codes for the representation of names of languages -- Part 2: Alpha-3 code,” October 1998.)
- "ISO 639-3:2007 - Codes for the representation of names of languages -- Part 3: Alpha-3 code for comprehensive coverage of languages" [ISO639‑3] (International Organization for Standardization, “ISO 639-3:2007. Codes for the representation of names of languages - Part 3: Alpha-3 code for comprehensive coverage of languages,” February 2007.)
- "ISO 639-5:2008 - Codes for the representation of names of languages -- Part 5: Alpha-3 code for language families and groups" [ISO639‑5] (International Organization for Standardization, “ISO 639-5:2008. Codes for the representation of names of languages -- Part 5: Alpha-3 code for language families and groups,” May 2008.)
When languages have both an ISO 639-1 two-character code and a three character code (assigned by ISO 639-2, ISO 639-3, or ISO 639-5), only the ISO 639-1 two-character code is defined in the IANA registry.
When languages that have no ISO 639-1 two-character code and for which the ISO 639-2/T (Terminology) code and the ISO 639-2/B (Bibliographic) codes differ, only the Terminology code is defined in the IANA registry. At the time this document was created, all languages that had both kinds of three-character code were also assigned a two-character code; it is expected that future assignments of this nature will not occur.
In order to avoid instability in the canonical form of tags, if a two-character code is added to ISO 639-1 for a language for which a three-character code was already included in either ISO 639-2 or ISO 639-3, the two-character code MUST NOT be registered. See Section 3.4 (Stability of IANA Registry Entries).
For example, if some content were tagged with 'haw' (Hawaiian), which currently has no two-character code, the tag would not need to be changed if ISO 639-1 were to assign a two-character code to the Hawaiian language at a later date.
To avoid these problems with versioning and subtag choice (as experienced during the transition between RFC 1766 and RFC 3066), as well as to ensure the canonical nature of subtags defined by this document, the ISO 639 Registration Authority Joint Advisory Committee (ISO 639/RA-JAC) has included the following statement in [iso639.prin] (ISO 639 Joint Advisory Committee, “ISO 639 Joint Advisory Committee: Working principles for ISO 639 maintenance,” March 2000.):
"A language code already in ISO 639-2 at the point of freezing ISO 639-1 shall not later be added to ISO 639-1. This is to ensure consistency in usage over time, since users are directed in Internet applications to employ the alpha-3 code when an alpha-2 code for that language is not available."
Extended language subtags are used to identify certain specially-selected languages that, for various historical and compatibility reasons, are closely identified with or tagged using an existing primary language subtag. Extended language subtags are always used with their enclosing primary language subtag (indicated with a 'Prefix' field in the registry) when used to form the language tag. All languages that have an extended language subtag in the registry also have an identical primary language subtag record in the registry. This primary language subtag is RECOMMENDED for forming the language tag. The following rules apply to the extended language subtags:
For example, the macrolanguage Chinese ('zh') encompasses a number of languages. For compatibility reasons, each of these languages has both a primary and extended language subtag in the registry. A few selected examples of these include Gan Chinese ('gan'), Cantonese Chinese ('yue') and Mandarin Chinese ('cmn'). Each is encompassed by the macrolanguage 'zh' (Chinese). Therefore, they each have the prefix "zh" in their registry records. Thus Gan Chinese is represented with tags beginning "zh-gan" or "gan"; Cantonese with tags beginning either "yue" or "zh-yue"; and Mandarin Chinese with "zh-cmn" or "cmn". The language subtag 'zh' can still be used without an extended language subtag to label a resource as some unspecified variety of Chinese, while the primary language subtag ('gan', 'yue', 'cmn') is preferred to using the extended language form ("zh-gan", "zh-yue", "zh-cmn").
Script subtags are used to indicate the script or writing system variations that distinguish the written forms of a language or its dialects. The following rules apply to the script subtags:
For example: "sr-Latn" represents Serbian written using the Latin script.
Region subtags are used to indicate linguistic variations associated with or appropriate to a specific country, territory, or region. Typically, a region subtag is used to indicate variations such as regional dialects or usage, or region-specific spelling conventions. It can also be used to indicate that content is expressed in a way that is appropriate for use throughout a region, for instance, Spanish content tailored to be useful throughout Latin America.
The following rules apply to the region subtags:
- UN numeric codes assigned to 'macro-geographical (continental)' or sub-regions MUST be registered in the registry. These codes are not associated with an assigned ISO 3166-1 alpha-2 code and represent supra-national areas, usually covering more than one nation, state, province, or territory.
- UN numeric codes for 'economic groupings' or 'other groupings' MUST NOT be registered in the IANA registry and MUST NOT be used to form language tags.
- When ISO 3166-1 reassigns a code formerly used for one country or area to another country or area and that code already is present in the registry, the UN numeric code for that country or area MUST be registered in the registry as described in Section 3.4 (Stability of IANA Registry Entries) and MUST be used to form language tags that represent the country or region for which it is defined (rather than the recycled ISO 3166-1 code).
- UN numeric codes for countries or areas for which there is an associated ISO 3166-1 alpha-2 code in the registry MUST NOT be entered into the registry and MUST NOT be used to form language tags. Note that the ISO 3166-based subtag in the registry MUST actually be associated with the UN M.49 code in question.
- For historical reasons, the UN numeric code 830 (Channel Islands), which was not registered at the time this document was adopted and had, at that time, no corresponding ISO 3166-1 code, MAY be entered into the IANA registry via the process described in Section 3.5, provided no ISO 3166-1 code with that exact meaning has been previously registered.
- All other UN numeric codes for countries or areas that do not have an associated ISO 3166-1 alpha-2 code MUST NOT be entered into the registry and MUST NOT be used to form language tags. For more information about these codes, see Section 3.4 (Stability of IANA Registry Entries).
"de-AT" represents German ('de') as used in Austria ('AT').
"sr-Latn-RS" represents Serbian ('sr') written using Latin script ('Latn') as used in Serbia ('RS').
"es-419" represents Spanish ('es') appropriate to the UN-defined Latin America and Caribbean region ('419').
Variant subtags are used to indicate additional, well-recognized variations that define a language or its dialects that are not covered by other available subtags. The following rules apply to the variant subtags:
Variant subtag records in the language subtag registry MAY include one or more 'Prefix' (Section 3.1.8 (Prefix Field)) fields. Each 'Prefix' indicates a suitable sequence of subtags for forming (with other subtags, as appropriate) a language tag when using the variant.
Most variants that share a prefix are mutually exclusive. For example, the German orthographic variations '1996' and '1901' SHOULD NOT be used in the same tag, as they represent the dates of different spelling reforms. A variant that can meaningfully be used in combination with another variant SHOULD include a 'Prefix' field in its registry record that lists that other variant. For example, if another German variant 'example' were created that made sense to use with '1996', then 'example' should include two Prefix fields: "de" and "de-1996".
"sl-nedis" represents the Natisone or Nadiza dialect of Slovenian.
"de-CH-1996" represents German as used in Switzerland and as written using the spelling reform beginning in the year 1996 C.E.
Extensions provide a mechanism for extending language tags for use in various applications. They are intended to identify information which is commonly used in association with languages or language tags, but which is not part of language identification. See Section 3.7 (Extensions and the Extensions Registry). The following rules apply to extensions:
For example, if an extension were defined for the singleton 'r' and it defined the subtags shown, then the following tag would be a valid example: "en-Latn-GB-boont-r-extended-sequence-x-private"
Private use subtags are used to indicate distinctions in language important in a given context by private agreement. The following rules apply to private use subtags:
For example, suppose a group of scholars are studying some texts in medieval Greek. They might agree to use some collection of private-use subtags to identify different styles of writing in the texts. For example, they might use 'el-x-koine' for documents in the "common" style while using 'el-x-attic' for other documents that mimic the Attic style. These subtags would not be recognized by outside processes or systems, but might be useful in categorizing various texts for study by those in the group.
Do not confuse private-use subtags with what this document refers to as "subtags reserved for private use". The latter are subtags such as 'qaa', 'Qaaa', or 'AA' that are designated as codes for private use by one of the underlying ISO standards. Although their purpose is very similar, subtags reserved for private use are represented by records of the appropriate type in the registry and, thus, are syntactically "language", "script", or "region" subtags, rather than "private-use" subtags.
Prior to RFC 4646, whole language tags were registered according to the rules in RFC 1766 and/or RFC 3066. All of these registered tags remain valid as language tags.
Many of these registered tags were made redundant by the advent of either RFC 4646 or this document. A redundant tag is a grandfathered registration whose individual subtags appear with the same semantic meaning in the registry. For example, the tag "zh-Hant" (Traditional Chinese) can now be composed from the subtags 'zh' (Chinese) and 'Hant' (Han script traditional variant). These redundant tags are maintained in the registry as records of type "redundant", mostly as a matter of historical curiosity.
The remainder of the previously registered tags are "grandfathered". These tags are classified into two groups: 'regular' and 'irregular'.
Grandfathered tags that (appear to) match the 'langtag' production in Figure 1 (Language Tag ABNF) are considered 'regular' grandfathered tags. These tags either contain subtags that do not individually appear in the registry, or their subtags appear but with a different semantic meaning: each tag, in its entirety, represents a language or collection of languages.
Grandfathered tags that do not match the 'langtag' production in the ABNF and would otherwise be invalid are considered 'irregular' grandfathered tags. With the exception of "en-GB-oed", which is a variant of "en-GB", each of them, in its entirety, represents a language.
Many of the grandfathered tags have been superseded by the subsequent addition of new subtags: each superseded record contains a Preferred-Value field that ought to be used to form language tags representing that value. For example, the tag "art-lojban" is superseded by the primary language subtag 'jbo'.
Implementations sometimes need to describe their capabilities with regard to the rules and practices described in this document. Tags can be checked or verified in a number of ways, but two particular classes of tag conformance are formally defined here.
A tag is considered "well-formed" if it conforms to the ABNF (Syntax). Language tags may be well-formed in terms of syntax but not valid in terms of content. However, many operations involving language tags work well without knowing anything about the meaning or validity of the subtags.
A tag is considered "valid" if it satisfies these conditions:
Note that a tag's validity depends on the date of the registry used to validate the tag. A more recent copy of the registry might contain a subtag that an older version does not.
A tag is considered "valid" for a given extension (Extensions and the Extensions Registry) (as of a particular version, revision, and date) if it meets the criteria for "valid" above and also satisfies this condition:
Each subtag used in the extension part of the tag is valid according to the extension.
Older specifications or language tag implementations sometimes reference [RFC3066] (Alvestrand, H., “Tags for the Identification of Languages,” January 2001.). A wider array of tags was considered 'well-formed' under that document. Any tags that were valid for use under RFC 3066 are both 'well-formed' and 'valid' under this document's syntax; only invalid or illegal tags were well-formed by the early definition but no longer are. The language tag syntax under RFC 3066 was:
obs-language-tag = primary-subtag *( "-" subtag ) primary-subtag = 1*8ALPHA subtag = 1*8(ALPHA / DIGIT)
| Figure 2: RFC 3066 Language Tag Syntax |
Subtags designated for private use as well as private-use sequences introduced by the 'x' subtag are available for cases in which no assigned subtags are available and registration is not a suitable option. For example, one might use a tag such as "no-QQ", where 'QQ' is one of a range of private-use ISO 3166-1 codes to indicate an otherwise-undefined region. Users MUST NOT assign language tags that use subtags that do not appear in the registry other than in private-use sequences (such the subtag 'personal' in the tag "en-x-personal"). Besides not being 'valid', the user also risks collision with a future possible assignment or registrations.
Note well: although the 'Language-Tag' production appearing in this document is functionally equivalent to the one in [RFC4646] (Phillips, A. and M. Davis, “Tags for Identifying Languages,” September 2006.), it has been changed to prevent certain errors in well-formedness arising from the old 'grandfathered' production.
The IANA Language Subtag Registry ("the registry") contains a comprehensive list of all of the subtags valid in language tags. This allows implementers a straightforward and reliable way to validate language tags. The registry will be maintained so that, except for extension subtags, it is possible to validate all of the subtags that appear in a language tag under the provisions of this document or its revisions or successors. In addition, the meaning of the various subtags will be unambiguous and stable over time. (The meaning of private use subtags, of course, is not defined by the registry.)
This section defines the registry along with the maintenance and update procedures associated with it, as well as a registry for extensions to language tags (Section 3.7 (Extensions and the Extensions Registry)).
The IANA Language Subtag Registry is a machine-readable file in the format described in this section, plus copies of the registration forms approved in accordance with the process described in Section 3.5 (Registration Procedure for Subtags).
The existing registration forms for grandfathered and redundant tags taken from RFC 3066 have been maintained as part of the obsolete RFC 3066 registry. The subtags added to the registry by either [RFC4645] (Ewell, D., “Initial Language Subtag Registry,” September 2006.) or [draft‑4645bis] (Ewell, D., Ed., “Update to the Language Subtag Registry,” May 2009.) do not have separate registration forms (so no forms are archived for these additions).
The registry is a [Unicode] (Unicode Consortium, “The Unicode Consortium. The Unicode Standard, Version 5.0, (Boston, MA, Addison-Wesley, 2003. ISBN 0-321-49081-0),” January 2007.) text file and consists of a series of records in a format based on "record-jar" (described in [record‑jar] (Raymond, E., “The Art of Unix Programming,” 2003.)). Each record, in turn, consists of a series of fields that describe the various subtags and tags. The actual registry file is encoded using the UTF-8 (Yergeau, F., “UTF-8, a transformation format of ISO 10646,” November 2003.) [RFC3629] character encoding.
Each field can be considered a single, logical line of characters. Each field contains a 'field-name' and a 'field-body'. These are separated by a 'field-separator'. The field-separator is a COLON character (%x3A) plus any surrounding whitespace. Each field is terminated by the newline sequence CRLF. The text in each field MUST be in Unicode Normalization Form C (NFC).
A collection of fields forms a 'record'. Records are separated by lines containing only the sequence "%%" (%x25.25).
Although fields are logically a single line of text, each line of text in the file format is limited to 72 bytes in length. To accommodate this, the field-body can be split into a multiple-line representation; this is called "folding". Folding is done according to customary conventions for line-wrapping. This is typically on whitespace boundaries, but can occur between other characters when the value does not include spaces, such as when a language does not use whitespace between words. In any event, there MUST NOT be breaks inside a multibyte UTF-8 sequence nor in the middle of a combining character sequence. For more information, see [UAX14] (Freitag, A., “Unicode Standard Annex #14: Line Breaking Properties,” August 2006.).
Although the file format uses the Unicode character set and the file itself encoded using the UTF-8 encoding, fields are restricted to the printable characters from the US-ASCII (International Organization for Standardization, “ISO/IEC 646:1991, Information technology -- ISO 7-bit coded character set for information interchange.,” 1991.) [ISO646] repertoire unless otherwise indicated in the description of a specific field (Record and Field Definitions).
The format of the registry is described by the following ABNF (Crocker, D. and P. Overell, “Augmented BNF for Syntax Specifications: ABNF,” January 2008.) [RFC5234]. Character numbers (code points) are taken from Unicode and terminals in the ABNF productions are in terms of characters rather than bytes.
registry = record *("%%" CRLF record) record = 1*field field = ( field-name field-sep field-body CRLF ) field-name = (ALPHA / DIGIT) [*(ALPHA / DIGIT / "-") (ALPHA / DIGIT)] field-sep = *SP ":" *SP field-body = *([[*SP CRLF] 1*SP] 1*CHARS) CHARS = (%x21-10FFFF) ; Unicode code points
| Figure 3: Registry Format ABNF |
The sequence '..' (%x2E.2E) in a field-body denotes a range of values. Such a range represents all subtags of the same length that are in alphabetic or numeric order within that range, including the values explicitly mentioned. For example 'a..c' denotes the values 'a', 'b', and 'c' and '11..13' denotes the values '11', '12', and '13'.
All fields whose field-body contains a date value use the "full-date" format specified in [RFC3339] (Klyne, G., Ed. and C. Newman, “Date and Time on the Internet: Timestamps,” July 2002.). For example: "2004-06-28" represents June 28, 2004, in the Gregorian calendar.
There are three types of records in the registry: "File-Date", "Subtag", and "Tag".
The first record in the registry is always the "File-Date" record. This record occurs only once in the file and contains a single field whose field-name is "File-Date". The field-body of this record contains a date (see Section 5.1 (Language Subtag Registry)) making it possible to easily recognize different versions of the registry.
File-Date: 2004-06-28 %%
| Figure 4: Example of the File-Date Record |
Subsequent records contain multiple fields and represent information about either subtags or tags. Both types of record have identical structure, except that "Subtag" records contain a field with a field-name of "Subtag", while, unsurprisingly, "Tag" records contain a field with a field-name of "Tag". Field-names MUST NOT occur more than once per record, with the exception of the 'Description', 'Comments', and sometimes the 'Prefix' field.
Each record MUST contain at least one of each of the following fields:
Each record MAY also contain the following fields:
Future versions of this document might add additional fields to the registry; implementations SHOULD ignore fields found in the registry that are not defined in this document.
The field 'Type' contains the string identifying the record type it appears in. Values for the 'Type' field-body are: "language" (Section 2.2.1 (Primary Language Subtag)); "extlang" (Section 2.2.2 (Extended Language Subtags)); "script" (Section 2.2.3 (Script Subtag)); "region" (Section 2.2.4 (Region Subtag)); "variant" (Section 2.2.5 (Variant Subtags)); "grandfathered" or "redundant" (Section 2.2.8 (Grandfathered and Redundant Registrations)).
The field 'Subtag' contains the subtag defined in the record. The field 'Tag' appears in records whose 'Type' is either 'grandfathered' or 'redundant' and contains a tag registered under [RFC3066] (Alvestrand, H., “Tags for the Identification of Languages,” January 2001.).
The 'Subtag' field-body MUST follow the casing conventions described in Section 2.1.1 (Formatting of Language Tags). All subtags use lowercase letters in the field-body, with two exceptions:
Subtags whose 'Type' field is 'script' (in other words, subtags defined by ISO 15924) MUST use titlecase.
Subtags whose 'Type' field is 'region' (in other words, the non-numeric region subtags defined by ISO 3166-1) MUST use all uppercase.
The 'Tag' field-body MUST be formatted according to the rules described in Section 2.1.1 (Formatting of Language Tags).
The field 'Description' contains a description of the tag or subtag in the record. The 'Description' field MAY appear more than once per record. The 'Description' field MAY include the full range of Unicode characters. At least one of the 'Description' fields MUST be written or transcribed into the Latin script; additional 'Description' fields MAY be in any script or language.
The 'Description' field is used for identification purposes. Descriptions SHOULD contain all and only that information necessary to distinguish one subtag from others that it might be confused with. They are not intended to provide general background information, nor to provide all possible alternate names or designations. 'Description' fields don't necessarily represent the actual native name of the item in the record, nor are any of the descriptions guaranteed to be in any particular language (such as English or French, for example).
Descriptions in the registry that correspond to ISO 639, ISO 15924, ISO 3166-1, or UN M.49 codes are intended only to indicate the meaning of that identifier as defined in the source standard at the time it was added to the registry or as subsequently modified, within the bounds of the stability rules (Stability of IANA Registry Entries), via subsequent registration. The 'Description' does not replace the content of the source standard itself. 'Description' fields are not intended to be the localized English names for the subtags. Localization or translation of language tag and subtag descriptions is out of scope of this document.
For subtags taken from a source standard (such as ISO 639 or ISO 15924), the 'Description' fields in the record are also initially taken from that source standard. Multiple descriptions in the source standard are split into separate 'Description' fields. The source standard's descriptions MAY be edited or modified, either prior to insertion or via the registration process, and additional or extraneous descriptions omitted or removed. Each 'Description' field MUST be unique within the record in which it appears and formatting variations of the same description SHOULD NOT occur in that specific record. For example, while the ISO 639-1 code 'fy' has both the description "Western Frisian" and the description "Frisian, Western" in that standard, only one of these descriptions appears in the registry.
To help ensure that users do not become confused about which subtag to use, 'Description' fields assigned to a record of any specific type ('language', 'extlang', 'script', and so on) MUST be unique within that given record type with the following exception: if a particular 'Description' field occurs in multiple records of a given type, then at most one of the records can omit the 'Deprecated' field; all deprecated records that share a 'Description' MUST have the same 'Preferred-Value'; and all non-deprecated records MUST be that 'Preferred-Value'. This means that two records of the same type that share a 'Description' are also semantically equivalent and no more than one record with a given 'Description' is preferred for that meaning.
For example, consider the 'language' subtags 'zza' (Zaza) and 'diq' (Dimli). It so happens that 'zza' is a macrolanguage enclosing 'diq' and thus also has a description in ISO 639-3 of "Dimli". This description was edited to read "Dimli (macrolanguage)" in the registry record for 'zza' to prevent a collision.
By contrast, the subtags 'he' and 'iw' share a 'Description' value of "Hebrew"; this is permitted because 'iw' is deprecated and its 'Preferred-Value' is 'he'.
For fields of type 'language', the first 'Description' field appearing in the Registry corresponds whenever possible to the Reference Name assigned by ISO 639-3. This helps facilitate cross-referencing between ISO 639 and the registry.
When creating or updating a record due to the action of one of the source standards, the Language Subtag Reviewer MAY edit descriptions to correct irregularities in formatting (such as misspellings, inappropriate apostrophes or other punctuation, or excessive or missing spaces) prior to submitting the proposed record to the email@example.com list for consideration.
The field 'Deprecated' contains the date the record was deprecated and MAY be added, changed, or removed from any record via the maintenance process described in Section 3.3 (Maintenance of the Registry) or via the registration process described in Section 3.5 (Registration Procedure for Subtags). Usually, the addition of a 'Deprecated' field is due to the action of one of the standards bodies, such as ISO 3166, withdrawing a code. Although valid in language tags, subtags and tags with a 'Deprecated' field are deprecated and validating processors SHOULD NOT generate these subtags. Note that a record that contains a 'Deprecated' field and no corresponding 'Preferred-Value' field has no replacement mapping.
In some historical cases, it might not have been possible to reconstruct the original deprecation date. For these cases, an approximate date appears in the registry. Some subtags and some grandfathered or redundant tags were deprecated before the initial creation of the registry. The exact rules for this appear in Section 2 of [RFC4645] (Ewell, D., “Initial Language Subtag Registry,” September 2006.). Note that these records have a 'Deprecated' field with an earlier date then the corresponding 'Added' field!
The field 'Preferred-Value' contains a mapping between the record in which it appears and another tag or subtag (depending on the record's 'Type'). The value in this field is used for canonicalization (see Section 4.5 (Canonicalization of Language Tags)). In cases where the subtag or tag also has a 'Deprecated' field, then the 'Preferred-Value' is RECOMMENDED as the best choice to represent the value of this record when selecting a language tag.
Records containing a Preferred-Value fall into one of these four groups:
Records other than those of type 'extlang' that contain a 'Preferred-Value' field MUST also have a 'Deprecated' field. This field contains the date on which the tag or subtag was deprecated in favor of the preferred value.
For records of type 'extlang', the 'Preferred-Value' field appears without a corresponding 'Deprecated' field. An implementation MAY ignore these preferred value mappings, although if it ignores the mapping, it SHOULD do so consistently. It SHOULD also treat the Preferred-Value as equivalent to the mapped item. For example, the tags "zh-yue-Hant-HK" and "yue-Hant-HK" are semantically equivalent and ought to be treated as if they were the same tag.
Occasionally the deprecated code is preferred in certain contexts. For example, both "iw" and "he" can be used in the Java programming language, but "he" is converted on input to "iw", which is thus the canonical form in Java.
'Preferred-Value' mappings in records of type 'region' sometimes do not represent exactly the same meaning as the original value. There are many reasons for a country code to be changed, and the effect this has on the formation of language tags will depend on the nature of the change in question. For example, the region subtag 'YD' (Democratic Yemen) was deprecated in favor of the subtag 'YE' (Yemen) when those two countries unified in 1990.
A 'Preferred-Value' MAY be added to, changed, or removed from records according to the rules in Section 3.3 (Maintenance of the Registry). Addition, modification, or removal of a 'Preferred-Value' field in a record does not imply that content using the affected subtag needs to be retagged.
The 'Preferred-Value' fields in records of type "grandfathered" and "redundant" each contain an "extended language range" ([RFC4647] (Phillips, A. and M. Davis, “Matching of Language Tags,” September 2006.)) that is strongly RECOMMENDED for use in place of the record's value. In many cases, these mappings were created via deprecation of the tags during the period before [RFC4646] (Phillips, A. and M. Davis, “Tags for Identifying Languages,” September 2006.) was adopted. For example, the tag "no-nyn" was deprecated in favor of the ISO 639-1-defined language code 'nn'.
The 'Preferred-Value' field in subtag records of type "extlang" also contains an "extended language range". This allows the subtag to be deprecated in favor of either a single primary language subtag or a new language-extlang sequence.
Usually the addition, removal, or change of a Preferred-Value field for a subtag is done to reflect changes in one of the source standards. For example, if an ISO 3166-1 region code is deprecated in favor of another code, that SHOULD result in the addition of a Preferred-Value field.
Changes to one subtag can affect other subtags as well: when proposing changes to the registry, the Language Subtag Reviewer MUST review the registry for such effects and propose the necessary changes using the process in Section 3.5 (Registration Procedure for Subtags), although anyone MAY request such changes. For example:
Suppose that subtag 'XX' has a Preferred-Value of 'YY'. If 'YY' later changes to have a Preferred-Value of 'ZZ', then the Preferred-Value for 'XX' MUST also change to be 'ZZ'.
Suppose that a registered language subtag 'dialect' represents a language not yet available in any part of ISO 639. The later addition of a corresponding language code in ISO 639 SHOULD result in the addition of a Preferred-Value for 'dialect'.
The field 'Prefix' contains a valid language tag that is RECOMMENDED as one possible prefix to this record's subtag, perhaps with other subtags. That is, when including an extended language or a variant subtag that has at least one 'Prefix' in a language tag, the resulting tag SHOULD match at least one of the subtag's 'Prefix' fields using the "Extended Filtering" algorithm (see [RFC4647] (Phillips, A. and M. Davis, “Matching of Language Tags,” September 2006.)) and each of the subtags in that 'Prefix' SHOULD appear before the subtag itself.
The 'Prefix' field MUST appear exactly once in a record of type 'extlang'. The 'Prefix' field MAY appear multiple times (or not at all) in records of type 'variant'. Additional fields of this type MAY be added to a 'variant' record via the registration process, provided the 'variant' record already has at least one 'Prefix' field.
Each 'Prefix' field indicates a particular sequence of subtags that form a meaningful tag with this subtag. For example, the extended language subtag 'cmn' (Mandarin Chinese) only makes sense with its prefix 'zh' (Chinese). Similarly, 'rozaj' (Resian, a dialect of Slovenian) would be appropriate when used with its prefix 'sl' (Slovenian), while tags such as "is-1994" are not appropriate (and probably not meaningful). Although the prefix for 'rozaj' is "sl", other subtags might appear between them. For example, the tag "sl-IT-rozaj" (Slovenian, Italy, Resian) matches the Prefix "sl".
The 'Prefix' also indicates when variant subtags make sense when used together (many that otherwise share a 'Prefix' are mutually exclusive) and what the relative ordering of variants is supposed to be. For example, the variant '1994' (Standardized Resian orthography) has several 'Prefix' fields in the registry ("sl-rozaj", "sl-rozaj-biske", "sl-rozaj-njiva", "sl-rozaj-osojs", and "sl-rozaj-solba"). This not only indicates that '1994' is appropriate to use with each of these five Resian variant subtags ('rozaj', 'biske', 'njiva', 'osojs', and 'solba') but also that it SHOULD appear following any of these variants in a tag. Thus, the language tag ought to take the form "sl-rozaj-biske-1994" rather than "sl-1994-rozaj-biske" or "sl-rozaj-1994-biske".
If a record includes no 'Prefix' field, a 'Prefix' field MUST NOT be added to the record at a later date. Otherwise, changes (additions, deletions, or modifications) to the set of 'Prefix' fields MAY be registered, as long as they strictly widen the range of language tags that are recommended. For example, the Prefix "be-Latn" (Belarusian, Latin script) could be replaced by the Prefix "be" (Belarusian) but not by the Prefix "ru-Latn" (Russian, Latin script) or the Prefix "be-Latn-BY" (Belarusian, Latin script, Belarus), since these latter either change or narrow the range of suggested tags.
The field-body of the 'Prefix' field MUST NOT conflict with any 'Prefix' already registered for a given record. Such a conflict would occur when no valid tag could be constructed that would contain the prefix, such as when two subtags each have a 'Prefix' that contains the other subtag. For example, suppose that the subtag 'avariant' has the prefix "es-bvariant". Then the subtag 'bvariant' cannot given the prefix 'avariant', for that would require a tag of the form "es-avariant-bvariant-avariant", which would not be valid.
The field 'Suppress-Script' contains a script subtag (whose record appears in the registry). The field 'Suppress-Script' MUST appear only in records whose 'Type' field-body is either 'language' or 'extlang'. This field MUST NOT appear more than one time in a record.
This field indicates a script used to write the overwhelming majority of documents for the given language. The subtag for such a script therefore adds no distinguishing information to a language tag and thus SHOULD NOT be used for most documents in that language. Omitting the script subtag indicated by this field helps ensure greater compatibility between the language tags generated according to the rules in this document and language tags and tag processors or consumers based on RFC 3066. For example, virtually all Icelandic documents are written in the Latin script, making the subtag 'Latn' redundant in the tag "is-Latn".
Many language subtag records do not have a 'Suppress-Script' field. The lack of a 'Suppress-Script' might indicate that the language is customarily written in more than one script or that the language is not customarily written at all. It might also mean that sufficient information was not available when the record was created and thus remains a candidate for future registration.
The field 'Macrolanguage' contains a primary language subtag (whose record appears in the registry). This field indicates a language that encompasses this subtag's language according to assignments made by ISO 639-3.
ISO 639-3 labels some languages in the registry as "macrolanguages". ISO 639-3 defines the term "Macrolanguage" to mean "clusters of closely-related language varieties that [...] can be considered distinct individual languages, yet in certain usage contexts a single language identity for all is needed". These correspond to codes registered in ISO 639-2 as individual languages that were found to correspond to more than one language in ISO 639-3.
A language contained within a macrolanguage is called an "encompassed language". The record for each encompassed language contains a 'Macrolanguage' field in the registry; the macrolanguages themselves are not specially marked. Note that some encompassed languages have ISO 639-1 or ISO 639-2 codes.
The Macrolanguage field can only occur in records of type 'language' or 'extlang'. Only values assigned by ISO 639-3 will be considered for inclusion. Macrolanguage fields MAY be added or removed via the normal registration process whenever ISO 639-3 defines new values or withdraws old values. Macrolanguages are informational, and MAY be removed or changed if ISO 639-3 changes the values. For more information on the use of this field and choosing between macrolanguage and encompassed language subtags, see Section 4.1.1 (Tagging Encompassed Languages).
For example, the language subtags 'nb' (Norwegian Bokmal) and 'nn' (Norwegian Nynorsk) each have a Macrolanguage entry of 'no' (Norwegian). For more information see Section 4.1 (Choice of Language Tag).
The field 'Scope' contains classification information about a primary or extended language subtag derived from ISO 639. Most languages have a scope of 'individual', which means that the language is not a macrolanguage, collection, special code, or private use. That is, it is what one would normally consider to be 'a language'. Any primary or extended language subtag that has no 'Scope' field is an individual language.
Scope information can sometimes be helpful in selecting language tags, since it indicates the purpose or "scope" of the code assignment within ISO 639. The available values are:
The Scope field MAY appear in records of type 'language' or 'extlang'. Note that many of the prefixes for extended language subtags will have a Scope of 'macrolanguage' (although some will not) and that many languages that have a Scope of 'macrolanguage' will have extended language subtags associated with them.
The Scope field MAY be added, modified, or removed via the registration process, provided the change mirrors changes by ISO 639 to the assignment's classification. Such a change is expected to be rare.
For example, the primary language subtag 'zh' (Chinese) has a Scope of 'macrolanguage', while its enclosed language 'nan' (Min Nan Chinese) has a Scope of 'individual'. The special value 'und' (Undetermined) has a Scope of 'special'. The ISO 639-5 collection 'gem' (Germanic languages) has a Scope of 'collection'.
The field 'Comments' contains additional information about the record and MAY appear more than once per record. The field-body MAY include the full range of Unicode characters and is not restricted to any particular script. This field MAY be inserted or changed via the registration process and no guarantee of stability is provided.
The content of this field is not restricted, except by the need to register the information, the suitability of the request, and by reasonable practical size limitations. The primary reason for the 'Comments' field is subtag identification: to help distinguish the subtag from others with which it might be confused as an aid to usage. Large amounts of information about the use, history, or general background of a subtag are frowned upon, as these generally belong in a registration request rather than in the registry.
The Language Subtag Reviewer moderates the firstname.lastname@example.org mailing list, responds to requests for registration, and performs the other registry maintenance duties described in Section 3.3 (Maintenance of the Registry). Only the Language Subtag Reviewer is permitted to request IANA to change, update, or add records to the Language Subtag Registry. The Language Subtag Reviewer MAY delegate list moderation and other clerical duties as needed.
The Language Subtag Reviewer is appointed by the IESG for an indefinite term, subject to removal or replacement at the IESG's discretion. The IESG will solicit nominees for the position (upon adoption of this document or upon a vacancy) and then solicit feedback on the nominees' qualifications. Qualified candidates should be familiar with BCP 47 and its requirements; be willing to fairly, responsively, and judiciously administer the registration process; and be suitably informed about the issues of language identification so that the reviewer can assess the claims and draw upon the contributions of language experts and subtag requesters.
The subsequent performance or decisions of the Language Subtag Reviewer MAY be appealed to the IESG under the same rules as other IETF decisions (see [RFC2026] (Bradner, S., “The Internet Standards Process -- Revision 3,” October 1996.)). The IESG can reverse or overturn the decisions of the Language Subtag Reviewer, provide guidance, or take other appropriate actions.
Maintenance of the registry requires that, as codes are assigned or withdrawn by ISO 639, ISO 15924, ISO 3166, and UN M.49, the Language Subtag Reviewer MUST evaluate each change and determine the appropriate course of action according to the rules in this document. Such updates follow the registration process described in Section 3.5 (Registration Procedure for Subtags). Usually the Language Subtag Reviewer will start the process for the new or updated record by filling in the registration form and submitting it. If a change to one of these standards takes place and the Language Subtag Reviewer does not do this in a timely manner, then any interested party MAY submit the form. Thereafter the registration process continues normally.
Note that some registrations affect other subtags--perhaps more than one--as when a region subtag is being deprecated in favor of a new value. The Language Subtag Reviewer is responsible for ensuring that any such changes are properly registered, with each change requiring its own registration form.
The Language Subtag Reviewer MUST ensure that new subtags meet the requirements elsewhere in this document (and most especially in Section 3.4 (Stability of IANA Registry Entries)) or submit an appropriate registration form for an alternate subtag as described in that section. Each individual subtag affected by a change MUST be sent to the email@example.com list with its own registration form and in a separate message.
The stability of entries and their meaning in the registry is critical to the long-term stability of language tags. The rules in this section guarantee that a specific language tag's meaning is stable over time and will not change.
These rules specifically deal with how changes to codes (including withdrawal and deprecation of codes) maintained by ISO 639, ISO 15924, ISO 3166, and UN M.49 are reflected in the IANA Language Subtag Registry. Assignments to the IANA Language Subtag Registry MUST follow the following stability rules:
- Codes assigned by ISO 639-1 that do not conflict with existing two-letter primary language subtags and which have no corresponding three-letter primary defined in the registry are entered into the IANA registry as new records of type 'language'. Note that languages given an ISO 639-1 code cannot be given extended language subtags, even if encompassed by a macrolanguage.
- Codes assigned by ISO 639-3 or ISO 639-5 that do not conflict with existing three-letter primary language subtags and which do not have ISO 639-1 codes assigned (or expected to be assigned) are entered into the IANA registry as new records of type 'language'. Note that these two standards now comprise a superset of ISO 639-2 codes. Codes that have a defined "macrolanguage" mapping at the time of their registration MUST contain a "Macrolanguage" field.
- Codes assigned by ISO 639-3 MAY also be considered for an extended language subtag registration. Note that they MUST be assigned a primary language subtag record of type 'language' even when an 'extlang' record is proposed. When considering extended language subtag assignment, these criteria apply:
- If a language has a macrolanguage mapping, and that macrolanguage has other encompassed languages that are assigned extended language subtags, then the new language SHOULD have an 'extlang' record assigned to it as well. For example, any language with a macrolanguage of 'zh' or 'ar' would be assigned an 'extlang' record.
- 'Extlang' records SHOULD NOT be created for languages if other languages encompassed by the macrolanguage do not also include 'extlang' records. For example, if a new Serbo-Croatian ('sh') language were registered, it would not get an extlang record because other languages encompassed such as Serbian ('sr') do not include one in the registry.
- Sign languages SHOULD have an 'extlang' record with a 'Prefix' of 'sgn'.
- 'Extlang' records MUST NOT be created for items already in the registry. Extended language subtags will only be considered at the time of initial registration.
- Extended language subtag records MUST include the fields 'Prefix' and 'Preferred-Value' with field-values assigned as described in Section 2.2.2 (Extended Language Subtags).
- Any other codes assigned by ISO 639-2 that do not conflict with existing three-letter primary or extended language subtags and which do not have ISO 639-1 two-letter codes assigned are entered into the IANA registry as new records of type 'language'. This type of registration is not supposed to occur in the future.
- For example: the region code 'TL' was assigned to the country 'Timor-Leste', replacing the code 'TP' (which was assigned to 'East Timor' when it was under administration by Portugal). The subtag 'TP' remains valid in language tags, but its record contains the 'Preferred-Value' of 'TL' and its field 'Deprecated' contains the date the new code was assigned ('2004-07-06').
- For ISO 639 codes, if the newly assigned code's meaning is not represented by a subtag in the IANA registry, the Language Subtag Reviewer, as described in Section 3.5 (Registration Procedure for Subtags), SHALL prepare a proposal for entering in the IANA registry as soon as practical a registered language subtag as an alternate value for the new code. The form of the registered language subtag will be at the discretion of the Language Subtag Reviewer and MUST conform to other restrictions on language subtags in this document.
- For all subtags whose meaning is derived from an external standard (that is, by ISO 639, ISO 15924, ISO 3166-1, or UN M.49), if a new meaning is assigned to an existing code and the new meaning broadens the meaning of that code, then the meaning for the associated subtag MAY be changed to match. The meaning of a subtag MUST NOT be narrowed, however, as this can result in an unknown proportion of the existing uses of a subtag becoming invalid. Note: ISO 639 registration authority (RA) has adopted a similar stability policy.
- For ISO 15924 codes, if the newly assigned code's meaning is not represented by a subtag in the IANA registry, the Language Subtag Reviewer, as described in Section 3.5 (Registration Procedure for Subtags), SHALL prepare a proposal for entering in the IANA registry as soon as practical a registered variant subtag as an alternate value for the new code. The form of the registered variant subtag will be at the discretion of the Language Subtag Reviewer and MUST conform to other restrictions on variant subtags in this document.
- For ISO 3166-1 codes, if the newly assigned code's meaning is associated with the same UN M.49 code as another 'region' subtag, then the existing region subtag remains as the preferred value for that region and no new entry is created. A comment MAY be added to the existing region subtag indicating the relationship to the new ISO 3166-1 code.
- For ISO 3166-1 codes, if the newly assigned code's meaning is associated with a UN M.49 code that is not represented by an existing region subtag, then the Language Subtag Reviewer, as described in Section 3.5 (Registration Procedure for Subtags), SHALL prepare a proposal for entering the appropriate UN M.49 country code as an entry in the IANA registry.
- For ISO 3166-1 codes, if there is no associated UN numeric code, then the Language Subtag Reviewer SHALL petition the UN to create one. If there is no response from the UN within ninety days of the request being sent, the Language Subtag Reviewer SHALL prepare a proposal for entering in the IANA registry as soon as practical a registered variant subtag as an alternate value for the new code. The form of the registered variant subtag will be at the discretion of the Language Subtag Reviewer and MUST conform to other restrictions on variant subtags in this document. This situation is very unlikely to ever occur.
The procedure given here MUST be used by anyone who wants to use a subtag not currently in the IANA Language Subtag Registry or who wishes to add, modify, update, or remove information in existing records as permitted by this document.
Only subtags of type 'language' and 'variant' will be considered for independent registration of new subtags. Subtags needed for stability and subtags necessary to keep the registry synchronized with ISO 639, ISO 15924, ISO 3166, and UN M.49 within the limits defined by this document also use this process, as described in Section 3.3 (Maintenance of the Registry) and subject to stability provisions as described in Section 3.4 (Stability of IANA Registry Entries).
Registration requests are accepted relating to information in the 'Comments', 'Deprecated', 'Description', 'Prefix', 'Preferred-Value', or 'Suppress-Script' fields in a subtag's record as described in Section 3.4 (Stability of IANA Registry Entries). Changes to all other fields in the IANA registry are NOT permitted.
Registering a new subtag or requesting modifications to an existing tag or subtag starts with the requester filling out
the registration form reproduced below. Note that each response is not limited
in size so that the request can adequately describe the registration.
The fields in the "Record Requested" section need to follow the requirements in Section 3.1 (Format of the IANA Language Subtag Registry) before the record will be approved.
LANGUAGE SUBTAG REGISTRATION FORM 1. Name of requester: 2. E-mail address of requester: 3. Record Requested: Type: Subtag: Description: Prefix: Preferred-Value: Deprecated: Suppress-Script: Macrolanguage: Comments: 4. Intended meaning of the subtag: 5. Reference to published description of the language (book or article): 6. Any other relevant information:
| Figure 5: The Language Subtag Registration Form |
Examples of completed registration forms can be found in Appendix C (Examples of Registration Forms). A complete list of approved registration forms is online at http://www.iana.org/assignments/lang-subtags-templates/.
The subtag registration form MUST be sent to <firstname.lastname@example.org>. Registration requests receive a two-week review period before being approved and submitted to IANA for inclusion in the registry. If modifications are made to the request during the course of the registration process (such as corrections to meet the requirements in Section 3.1 (Format of the IANA Language Subtag Registry) or to make the 'Description' fields unique for the given record type) the modified form MUST also be sent to <email@example.com> at least one week prior to submission to IANA.
The ietf-languages list is an open list and can be joined by sending a request to <firstname.lastname@example.org>. The list can be hosted by IANA or by any third party at the request of IESG.
Before forwarding any registration to IANA, the Language Subtag Reviewer MUST ensure that all requirements in this document are met. This includes ensuring that values in the 'Subtag' field match case according to the description in Section 3.1.4 (Subtag and Tag Fields) and that 'Description' fields are unique for the given record type as described in Section 3.1.5 (Description Field). The Reviewer MUST also ensure that an appropriate File-Date record is included in the request, to assist IANA when updating the registry (see Section 5.1 (Language Subtag Registry)).
Some fields in both the registration form as well as the registry record itself permit the use of non-ASCII characters. Registration requests SHOULD use the UTF-8 encoding for consistency and clarity. However, since some mail clients do not support this encoding, other encodings MAY be used for the registration request. The Language Subtag Reviewer is responsible for ensuring that the proper Unicode characters appear in both the archived request form and the registry record. In the case of a transcription or encoding error by IANA, the Language Subtag Reviewer will request that the registry be repaired, providing any necessary information to assist IANA.
Extended language subtags (type 'extlang'), by definition, are always encompassed by another language. All records of type 'extlang' MUST, therefore, contain a 'Prefix' field at the time of registration. This Prefix field can never be altered or removed and requests to do so MUST be rejected.
Variant subtags are usually registered for use with a particular range of language tags and variant subtags based on the terminology of the language to which they are apply are encouraged. For example, the subtag 'rozaj' (Resian) is intended for use with language tags that start with the primary language subtag "sl" (Slovenian), since Resian is a dialect of Slovenian. Thus, the subtag 'rozaj' would be appropriate in tags such as "sl-Latn-rozaj" or "sl-IT-rozaj". This information is stored in the 'Prefix' field in the registry. Variant registration requests SHOULD include at least one 'Prefix' field in the registration form.
Requests to assign an additional record of a given type with an existing subtag value MUST be rejected. For example, the variant subtag 'rozaj' already exists in the registry, so adding a second record of type 'variant' with the subtag 'rozaj' is prohibited.
The 'Prefix' field for a given registered variant subtag exists in the IANA registry as a guide to usage. Additional 'Prefix' fields MAY be added by filing an additional registration form. In that form, the "Any other relevant information:" field MUST indicate that it is the addition of a prefix.
Requests to add a 'Prefix' field to a variant subtag that imply a different semantic meaning SHOULD be rejected. For example, a request to add the prefix "de" to the subtag '1994' so that the tag "de-1994" represented some German dialect or orthographic form would be rejected. The '1994' subtag represents a particular Slovenian orthography and the additional registration would change or blur the semantic meaning assigned to the subtag. A separate subtag SHOULD be proposed instead.
Requests to add a 'Prefix' to a variant subtag that has no current 'Prefix' field MUST be rejected. Variants are registered with no prefix because they are potentially useful with many or even all languages. Adding one or more 'Prefix' fields would be potentially harmful to the use of the variant, since it dramatically reduces the scope of the subtag (which is not allowed under the stability rules (Stability of IANA Registry Entries), as opposed to broadening the scope of the subtag, which is what the addition of a 'Prefix' normally does. An example of such a "no-prefix" variant is the subtag 'fonipa', which represents the International Phonetic Alphabet, a scheme which can be used to transcribe many languages.
The 'Description' fields provided in the request MUST contain at least one description written or transcribed into the Latin script; the request MAY also include additional 'Description' fields in any script or language. The 'Description' field is used for identification purposes and doesn't necessarily represent the actual native name of the language or variation. It also doesn't have to be in any particular language, but SHOULD be both suitable and sufficient to identify the item in the record. The Language Subtag Reviewer will check and edit any proposed 'Description' fields so as to ensure uniqueness and prevent collisions with 'Description' fields in other records of the same type. If this occurs in an independent registration request, the Language Subtag Reviewer MUST resubmit the record to email@example.com, treating it as a modification of a request due to discussion, as described in Section 3.5 (Registration Procedure for Subtags), unless the request's sole purpose is to introduce a duplicate 'Description' field, in which case the request SHALL be rejected.
While the 'Description' field itself is not guaranteed to be stable and errata corrections MAY be undertaken from time to time, attempts to provide translations or transcriptions of entries in the registry itself will probably be frowned upon by the community or rejected outright, as changes of this nature have an impact on the provisions in Section 3.4 (Stability of IANA Registry Entries).
Soon after the two-week review period has passed, the Language Subtag Reviewer MUST take one of the following actions:
Note that the Language Subtag Reviewer MAY raise objections on the list if he or she so desires. The important thing is that the objection MUST be made publicly.
Sometimes the request needs to be modified as a result of discussion during the review period or due to requirements in this document. The applicant, Language Subtag Reviewer, or others MAY submit a modified version of the completed registration form, which will be considered in lieu of the original request with the explicit approval of the applicant. Such changes do not restart the two-week discussion period, although an application containing the final record submitted to IANA MUST appear on the list at least one week prior to the Language Subtag Reviewer forwarding the record to IANA. The applicant MAY modify a rejected application with more appropriate or additional information and submit it again; this starts a new two-week comment period.
Registrations initiated due to the provisions of Section 3.3 (Maintenance of the Registry) or Section 3.4 (Stability of IANA Registry Entries) SHALL NOT be rejected altogether (since they have to ultimately appear in the registry) and SHOULD be completed as quickly as possible. The review process allows list members to comment on the specific information in the form and the record it contains and thus help ensure that it is correct and consistent. The Language Subtag Reviewer MAY reject a specific version of the form, but MUST propose a suitable replacement, extending the review period as described above, until the form is in a format worthy of reviewer's approval and meets with rough consensus of the list.
Decisions made by the Language Subtag Reviewer MAY be appealed to the IESG [RFC2028] (Hovey, R. and S. Bradner, “The Organizations Involved in the IETF Standards Process,” October 1996.) under the same rules as other IETF decisions [RFC2026] (Bradner, S., “The Internet Standards Process -- Revision 3,” October 1996.). This includes a decision to extend the review period or the failure to announce a decision in a clear and timely manner.
The approved records appear in the Language Subtag Registry. The approved registration forms are available online under http://www.iana.org/assignments/lang-subtags-templates/.
Updates or changes to existing records follow the same procedure as new registrations. The Language Subtag Reviewer decides whether there is consensus to update the registration following the two week review period; normally, objections by the original registrant will carry extra weight in forming such a consensus.
Registrations are permanent and stable. Once registered, subtags will not be removed from the registry and will remain a valid way in which to specify a specific language or variant.
Note: The purpose of the "Reference to published description" section in the registration form is to aid in verifying whether a language is registered or what language or language variation a particular subtag refers to. In most cases, reference to an authoritative grammar or dictionary of that language will be useful; in cases where no such work exists, other well-known works describing that language or in that language MAY be appropriate. The Language Subtag Reviewer decides what constitutes "good enough" reference material. This requirement is not intended to exclude particular languages or dialects due to the size of the speaker population or lack of a standardized orthography. Minority languages will be considered equally on their own merits.
Possibilities for registration of subtags or information about subtags include:
Subtags proposed for registration that would cause all or part of a grandfathered tag to become redundant but whose meaning conflicts with or alters the meaning of the grandfathered tag MUST be rejected.
This document leaves the decision on what subtags or changes to subtags are appropriate (or not) to the registration process described in Section 3.5 (Registration Procedure for Subtags).
Note: four-character primary language subtags are reserved to allow for the possibility of alpha4 codes in some future addition to the ISO 639 family of standards.
ISO 639 defines a registration authority for additions to and changes in the list of languages in ISO 639. This agency is:
International Information Centre for Terminology (Infoterm)
Aichholzgasse 6/12, AT-1120
Phone: +43 1 26 75 35 Ext. 312 Fax: +43 1 216 32 72
ISO 639-2 defines a registration authority for additions to and changes in the list of languages in ISO 639-2. This agency is:
Library of Congress
Network Development and MARC Standards Office
Washington, D.C. 20540 USA
Phone: +1 202 707 6237 Fax: +1 202 707 0115
ISO 639-3 defines a registration authority for additions to and changes in the list of languages in ISO 639-3. This agency is:
ISO 639-3 Registrar
7500 W. Camp Wisdom Rd.
Dallas, TX 75236 USA
Phone: +1 972 708 7400, ext. 2293 Fax: +1 972 708 7546
ISO 639-5 defines a registration authority for additions to and changes in the list of languages in ISO 639-5. This agency is the same as for ISO 639-2 and is:
Library of Congress
Network Development and MARC Standards Office
Washington, D.C. 20540 USA
Phone: +1 202 707 6237 Fax: +1 202 707 0115
The maintenance agency for ISO 3166-1 (country codes) is:
ISO 3166 Maintenance Agency
c/o International Organization for Standardization
Case postale 56
CH-1211 Geneva 20 Switzerland
Phone: +41 22 749 72 33 Fax: +41 22 749 73 49
The registration authority for ISO 15924 (script codes) is:
Mountain View, CA 94039-1476, USA
The Statistics Division of the United Nations Secretariat maintains the Standard Country or Area Codes for Statistical Use and can be reached at:
Statistical Services Branch
United Nations, Room DC2-1620
New York, NY 10017, USA
Extension subtags are those introduced by single-character subtags ("singletons") other than 'x'. They are reserved for the generation of identifiers that contain a language component and are compatible with applications that understand language tags.
The structure and form of extensions are defined by this document so that implementations can be created that are forward compatible with applications that might be created using singletons in the future. In addition, defining a mechanism for maintaining singletons will lend stability to this document by reducing the likely need for future revisions or updates.
Single-character subtags are assigned by IANA using the "IETF Review" policy defined by [RFC5226] (Narten, T. and H. Alvestrand, “Guidelines for Writing an IANA Considerations Section in RFCs,” May 2008.). This policy requires the development of an RFC, which SHALL define the name, purpose, processes, and procedures for maintaining the subtags. The maintaining or registering authority, including name, contact email, discussion list email, and URL location of the registry, MUST be indicated clearly in the RFC. The RFC MUST specify or include each of the following:
IANA will maintain a registry of allocated single-character (singleton) subtags. This registry MUST use the record-jar format described by the ABNF in Section 3.1 (Format of the IANA Language Subtag Registry). Upon publication of an extension as an RFC, the maintaining authority defined in the RFC MUST forward this registration form to firstname.lastname@example.org, who MUST forward the request to email@example.com. The maintaining authority of the extension MUST maintain the accuracy of the record by sending an updated full copy of the record to firstname.lastname@example.org with the subject line "LANGUAGE TAG EXTENSION UPDATE" whenever content changes. Only the 'Comments', 'Contact_Email', 'Mailing_List', and 'URL' fields MAY be modified in these updates.
Failure to maintain this record, maintain the corresponding registry, or meet other conditions imposed by this section of this document MAY be appealed to the IESG [RFC2028] (Hovey, R. and S. Bradner, “The Organizations Involved in the IETF Standards Process,” October 1996.) under the same rules as other IETF decisions (see [RFC2026] (Bradner, S., “The Internet Standards Process -- Revision 3,” October 1996.)) and MAY result in the authority to maintain the extension being withdrawn or reassigned by the IESG.
%% Identifier: Description: Comments: Added: RFC: Authority: Contact_Email: Mailing_List: URL: %%
| Figure 6: Format of Records in the Language Tag Extensions Registry |
'Identifier' contains the single-character subtag (singleton) assigned to the extension. The Internet-Draft submitted to define the extension SHOULD specify which letter or digit to use, although the IESG MAY change the assignment when approving the RFC.
'Description' contains the name and description of the extension.
'Comments' is an OPTIONAL field and MAY contain a broader description of the extension.
'Added' contains the date the extension's RFC was published in the "full-date" format specified in [RFC3339] (Klyne, G., Ed. and C. Newman, “Date and Time on the Internet: Timestamps,” July 2002.). For example: 2004-06-28 represents June 28, 2004, in the Gregorian calendar.
'RFC' contains the RFC number assigned to the extension.
'Authority' contains the name of the maintaining authority for the extension.
'Contact_Email' contains the email address used to contact the maintaining authority.
'Mailing_List' contains the URL or subscription email address of the mailing list used by the maintaining authority.
'URL' contains the URL of the registry for this extension.
The determination of whether an Internet-Draft meets the above conditions and the decision to grant or withhold such authority rests solely with the IESG and is subject to the normal review and appeals process associated with the RFC process.
Extension authors are strongly cautioned that many (including most well-formed) processors will be unaware of any special relationships or meaning inherent in the order of extension subtags. Extension authors SHOULD avoid subtag relationships or canonicalization mechanisms that interfere with matching or with length restrictions that sometimes exist in common protocols where the extension is used. In particular, applications MAY truncate the subtags in doing matching or in fitting into limited lengths, so it is RECOMMENDED that the most significant information be in the most significant (left-most) subtags and that the specification gracefully handle truncated subtags.
When a language tag is to be used in a specific, known, protocol, it is RECOMMENDED that the language tag not contain extensions not supported by that protocol. In addition, note that some protocols MAY impose upper limits on the length of the strings used to store or transport the language tag.
Upon adoption of this document the IANA Language Subtag Registry will need an update so that it contains the complete set of subtags valid in a language tag. This collection of subtags, along with a description of the process used to create it, is described by [draft‑4645bis] (Ewell, D., Ed., “Update to the Language Subtag Registry,” May 2009.). Once published by IANA, the maintenance procedures, rules, and registration processes described in this document will be available for new registrations or updates.RFC Editor: please modify this paragraph upon publication to reflect the fact that RFC 4645bis has also been published (past tense).
Registrations that are in process under the rules defined in [RFC4646] (Phillips, A. and M. Davis, “Tags for Identifying Languages,” September 2006.) when this document is adopted MUST be completed under the rules contained in this document.
This section addresses how to use the information in the registry with the tag syntax to choose, form, and process language tags.
The guiding principle in forming language tags is to "tag content wisely." Sometimes there is a choice between several possible tags for the same content. The choice of which tag to use depends on the content and application in question and some amount of judgment might be necessary when selecting a tag.
Interoperability is best served when the same language tag is used consistently to represent the same language. If an application has requirements that make the rules here inapplicable, then that application risks damaging interoperability. It is strongly RECOMMENDED that users not define their own rules for language tag choice.
Standards, protocols, and applications that reference this document normatively but apply different rules to the ones given in this section MUST specify how language tag selection varies from the guidelines given here.
To ensure consistent backward compatibility, this document contains several provisions to account for potential instability in the standards used to define the subtags that make up language tags. These provisions mean that no valid language tag can become invalid, nor will a language tag have a narrower scope in the future (it may have a broader scope). The most appropriate language tag for a given application or content item might evolve over time, but once applied, the tag itself cannot become invalid or have its meaning wholly change.
A subtag SHOULD only be used when it adds useful distinguishing information to the tag. Extraneous subtags interfere with the meaning, understanding, and processing of language tags. In particular, users and implementations SHOULD follow the 'Prefix' and 'Suppress-Script' fields in the registry (defined in Section 3.1 (Format of the IANA Language Subtag Registry)): these fields provide guidance on when specific additional subtags SHOULD be used or avoided in a language tag.
The choice of subtags used to form a language tag SHOULD follow these guidelines:
- For example, the tag "en-scottish-fonipa" (English, Scottish dialect, IPA phonetic transcription) is correctly ordered because 'scottish' has a 'Prefix' of "en", while 'fonipa' has no 'Prefix' field.
- For example, the tag "sl-IT-rozaj-biske-1994" is correctly ordered: 'rozaj' lists "sl" as its sole 'Prefix'; 'biske' lists "sl-rozaj" as its sole Prefix. The subtag '1994' has several prefixes, including "sl-rozaj". However, it follows both 'rozaj' and 'biske' because one of its 'Prefix' fields is "sl-rozaj-biske".
Some primary language records in the registry have a "Macrolanguage" field (Section 3.1.10 (Macrolanguage Field)) that contains a mapping from each "encompassed language" to its macrolanguage. The Macrolanguage mapping doesn't define what the relationship between the encompassed language and its macrolanguage is, nor does it define how languages encompassed by the same macrolanguage are related to each other. Two different languages encompassed by the same macrolanguage may differ from one another more than say, French and Spanish do.
A few specific macrolanguages, such as Chinese ('zh') and Arabic ('ar'), are handled differently. See Section 4.1.2 (Using Extended Language Subtags).
The more specific encompassed language subtag SHOULD be used to form the language tag, although either the macrolanguage's primary language subtag or the encompassed language's subtag MAY be used. This means, for example, tagging Plains Cree with 'crk' rather than 'cre' (Cree); and so forth.
Each macrolanguage subtag's scope, by definition, includes all of its encompassed languages. Since the relationship between encompassed languages varies, users cannot assume that the macrolanguage subtag means any particular encompassed language nor that any given pair of encompassed languages are mutually intelligible or otherwise interchangeable.
Applications MAY use macrolanguage information to improve matching or language negotiation. For example, the information that 'sr' (Serbian) and 'hr' (Croatian) share a macrolanguage expresses a closer relation between those languages than between, say, 'sr' (Serbian) and 'ma' (Macedonian). However, this relationship is not guaranteed nor is it exclusive. For example, Romanian ('ro') and Moldavian ('mo') do not share a macrolanguage, but are far more closely related to each other than Cantonese ('yue') and Wu ('wuu') , which do share a macrolanguage.
To accommodate language tag forms used prior to the adoption of this document, language tags provide a special compatibility mechanism: the extended language subtag. Selected languages have been provided with both primary and extended language subtags. These include macrolanguages, such as Malay ('ms') and Uzbek ('uz'), that have a specific dominant variety that is generally synonymous with the macrolanguage. Other languages, such as the Chinese ('zh') and Arabic ('ar') macrolanguages and the various sign languages ('sgn'), have traditionally used their primary language subtag, possibly coupled with various region subtags or as part of a registered grandfathered tag, to indicate the language.
With the adoption of this document, specific ISO 639-3 subtags became available to identify the languages contained within these diverse language families or groupings. This presents a choice of language tags where previously none existed:
Chinese ('zh') provides a useful illustration of this. In the past, various content has used tags beginning with the 'zh' subtag, with application specific meaning being associated with region codes, private-use sequences, or grandfathered registered values. This is because historically only the macrolanguage subtag 'zh' was available for forming language tags. However, the languages encompassed by the Chinese subtag 'zh' are, in the main, not mutually intelligible when spoken, and the written forms of these languages also show wide variation in form and usage.
To provide compatibility, Chinese languages encompassed by the 'zh' subtag are in the registry as both primary language subtags and as extended language subtags. For example, the ISO 639-3 code for Cantonese is 'yue'. Content in Cantonese might historically have used a tag such as "zh-HK" (since Cantonese is commonly spoken in Hong Kong), although that tag actually means any type of Chinese as used in Hong Kong. With the availability of ISO 639-3 codes in the registry, content in Cantonese can be directly tagged using the 'yue' subtag. The content can use it as a primary language subtag, as in the tag "yue-HK" (Cantonese, Hong Kong). Or it can use an extended language subtag with 'zh', as in the tag "zh-yue-Hant" (Chinese, Cantonese, Traditional script).
As noted above, applications can choose to use the macrolanguage subtag to form the tag instead of using the more specific encompassed language subtag. For example, an application with large quantities of data already using tags with the 'zh' (Chinese) subtag might continue to use this more general subtag even for new data, even though the content could be more precisely tagged with 'cmn' (Mandarin), 'yue' (Cantonese), 'wuu' (Wu), and so on. Similarly, an application already using tags that start with the 'ar' (Arabic) subtag might continue to use this more general subtag even for new data, which could be more precisely be tagged with 'arb' (Standard Arabic).
In some cases, the encompassed languages had tags registered for them during the RFC 3066 era. Those grandfathered tags not already deprecated or rendered redundant were deprecated in the registry upon adoption of this document. As grandfathered values, they remain valid for use and some content or applications might use them. As with other grandfathered tags, since implementations might not be able to associate the grandfathered tags with the encompassed language subtag equivalents that are recommended by this document, implementations are encouraged to canonicalize tags for comparison purposes. Some examples of this include the tags "zh-hakka" (Hakka) and "zh-guoyu" (Mandarin or Standard Chinese).
Sign languages share a mode of communication rather than a linguistic heritage. There are many sign languages which have developed independently and the subtag 'sgn' indicates only the presence of a sign language. A number of sign languages also had grandfathered tags registered for them during the RFC 3066 era. For example, the grandfathered tag "sgn-US" was registered to represent 'American Sign Language' specifically, without reference to the United States. This is still valid, but deprecated: a document in American Sign Language can be labeled either "ase" or "sgn-ase" (the 'ase' subtag is for the language called 'American Sign Language').
The meaning of a language tag is related to the meaning of the subtags that it contains. Each subtag, in turn, implies a certain range of expectations one might have for related content, although it is not a guarantee. For example, the use of a script subtag such as 'Arab' (Arabic script) does not mean that the content contains only Arabic characters. It does mean that the language involved is predominantly in the Arabic script. Thus a language tag and its subtags can encompass a very wide range of variation and yet remain appropriate in each particular instance.
Validity of a tag is not the only factor determining its usefulness. While every valid tag has a meaning, it might not represent any real-world language usage. This is unavoidable in a system in which subtags can be combined freely. For example, tags such as "ar-Cyrl-CO" (Arabic, Cyrillic script, as used in Colombia) or "tlh-Kore-AQ-fonipa" (Klingon, Korean script, as used in Antarctica, IPA phonetic transcription) are both valid and unlikely to represent a useful combination of language attributes.
The meaning of a given tag doesn't depend on the context in which it appears. The relationship between a tag's meaning and the information objects to which that tag is applied, however, can vary.
Language tags are related when they contain a similar sequence of subtags. For example, if a language tag B contains language tag A as a prefix, then B is typically "narrower" or "more specific" than A. Thus, "zh-Hant-TW" is more specific than "zh-Hant".
This relationship is not guaranteed in all cases: specifically, languages that begin with the same sequence of subtags are NOT guaranteed to be mutually intelligible, although they might be. For example, the tag "az" shares a prefix with both "az-Latn" (Azerbaijani written using the Latin script) and "az-Cyrl" (Azerbaijani written using the Cyrillic script). A person fluent in one script might not be able to read the other, even though the linguistic content (e.g., what would be heard if both texts were read aloud) might be identical. Content tagged as "az" most probably is written in just one script and thus might not be intelligible to a reader familiar with the other script.
Similarly, not all subtags specify an actual distinction in language. For example, the tags "en-US" and "en-CA" mean, roughly, English with features generally thought to be characteristic of the United States and Canada, respectively. They do not imply that a significant dialectical boundary exists between any arbitrarily selected point in the United States and any arbitrarily selected point in Canada. Neither does a particular region subtag imply that linguistic distinctions do not exist within that region.
In some applications, a single content item might best be associated with more than one language tag. Examples of such a usage include:
There is no defined upper limit on the size of language tags. While historically most language tags have consisted of language and region subtags with a combined total length of up to six characters, larger tags have always been both possible and have actually appeared in use.
Neither the language tag syntax nor other requirements in this document impose a fixed upper limit on the number of subtags in a language tag (and thus an upper bound on the size of a tag). The language tag syntax suggests that, depending on the specific language, more subtags (and thus a longer tag) are sometimes necessary to completely identify the language for certain applications; thus, it is possible to envision long or complex subtag sequences.
Some applications and protocols are forced to allocate fixed buffer sizes or otherwise limit the length of a language tag. A conformant implementation or specification MAY refuse to support the storage of language tags that exceed a specified length. Any such limitation SHOULD be clearly documented, and such documentation SHOULD include what happens to longer tags (for example, whether an error value is generated or the language tag is truncated). A protocol that allows tags to be truncated at an arbitrary limit, without giving any indication of what that limit is, has the potential for causing harm by changing the meaning of tags in substantial ways.
In practice, most language tags do not require more than a few subtags and will not approach reasonably sized buffer limitations; see Section 4.1 (Choice of Language Tag).
Some specifications or protocols have limits on tag length but do not have a fixed length limitation. For example, [RFC2231] (Freed, N. and K. Moore, “MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations,” November 1997.) has no explicit length limitation: the length available for the language tag is constrained by the length of other header components (such as the charset's name) coupled with the 76-character limit in [RFC2047] (Moore, K., “MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text,” November 1996.). Thus, the "limit" might be 50 or more characters, but it could potentially be quite small.
The considerations for assigning a buffer limit are:
Implementations SHOULD NOT truncate language tags unless the meaning of the tag is purposefully being changed, or unless the tag does not fit into a limited buffer size specified by a protocol for storage or transmission.
Implementations SHOULD warn the user when a tag is truncated since truncation changes the semantic meaning of the tag.
Implementations of protocols or specifications that are space constrained but do not have a fixed limit SHOULD use the longest possible tag in preference to truncation.
Protocols or specifications that specify limited buffer sizes for language tags MUST allow for language tags of at least 35 characters. Note that RFC 4646 (Phillips, A. and M. Davis, “Tags for Identifying Languages,” September 2006.) [RFC4646] recommended a minimum field size of 42 characters because it included all three elements of the 'extlang' production. Two of these are now permanently reserved, so a registered primary language subtag of the maximum length of eight characters is now longer than the longest language-extlang combination. Protocols or specifications that commonly use extensions or private use subtags might wish to reserve or recommend a longer "minimum buffer" size.
The following illustration shows how the 35-character recommendation was derived:
language = 8 ; longest allowed registered value ; longer than primary+extlang ; which requires 7 characters script = 5 ; if not suppressed: see Section 4.1 region = 4 ; UN M.49 numeric region code ; ISO 3166-1 codes require 3 variant1 = 9 ; needs 'language' as a prefix variant2 = 9 ; very rare, as it needs ; 'language-variant1' as a prefix total = 35 characters
| Figure 7: Derivation of the Limit on Tag Length |
Truncation of a language tag alters the meaning of the tag, and thus SHOULD be avoided. However, truncation of language tags is sometimes necessary due to limited buffer sizes. Such truncation MUST NOT permit a subtag to be chopped off in the middle or the formation of invalid tags (for example, one ending with the "-" character).
This means that applications or protocols that truncate tags MUST do so by progressively removing subtags along with their preceding "-" from the right side of the language tag until the tag is short enough for the given buffer. If the resulting tag ends with a single-character subtag, that subtag and its preceding "-" MUST also be removed. For example:
Tag to truncate: zh-Latn-CN-variant1-a-extend1-x-wadegile-private1 1. zh-Latn-CN-variant1-a-extend1-x-wadegile 2. zh-Latn-CN-variant1-a-extend1 3. zh-Latn-CN-variant1 4. zh-Latn-CN 5. zh-Latn 6. zh
| Figure 8: Example of Tag Truncation |
Since a particular language tag can be used by many processes, language tags SHOULD always be created or generated in canonical form.
A language tag is in 'canonical form' when the tag is well-formed according to the rules in Section 2.1 (Syntax) and Section 2.2 (Language Subtag Sources and Interpretation) and it has been canonicalized by applying each of the following steps in order, using data from the IANA registry (see Section 3.1 (Format of the IANA Language Subtag Registry)):
The canonical form contains no 'extlang' subtags. There is an alternate 'extlang form' that maintains or reinstates extlang subtags. This form can be useful in environments where the presence of the Prefix subtag is considered beneficial in matching or selection (see Section 4.1.2 (Using Extended Language Subtags)).
A language tag is in 'extlang form', when the tag is well-formed according to the rules in Section 2.1 (Syntax) and Section 2.2 (Language Subtag Sources and Interpretation) and it has been processed by applying each of the following two steps in order, using data from the IANA registry:
Example: The language tag "en-a-aaa-b-ccc-bbb-x-xyz" is in canonical form, while "en-b-ccc-bbb-a-aaa-X-xyz" is well-formed and potentially valid (extensions 'a' and 'b' are not defined as of the publication of this document) but not in a canonical form (the extensions are not in alphabetical order).
Example: Although the tag "en-BU" (English as used in Burma) maintains its validity, the language tag "en-BU" is not in canonical form because the 'BU' subtag has a canonical mapping to 'MM' (Myanmar).
Canonicalization of language tags does not imply anything about the use of upper or lowercase letters when processing or comparing subtags (and as described in Section 2.1 (Syntax)). All comparisons MUST be performed in a case-insensitive manner.
When performing canonicalization of language tags, processors MAY regularize the case of the subtags (that is, this process is OPTIONAL), following the case used in the registry (see Section 2.1.1 (Formatting of Language Tags)).
If more than one variant appears within a tag, processors MAY reorder the variants to obtain better matching behavior or more consistent presentation. Reordering of the variants SHOULD follow the recommendations for variant ordering in Section 4.1 (Choice of Language Tag).
If the field 'Deprecated' appears in a registry record without an accompanying 'Preferred-Value' field, then that tag or subtag is deprecated without a replacement. These values are canonical when they appear in a language tag. However, tags that include these values SHOULD NOT be selected by users or generated by implementations.
An extension MUST define any relationships that exist between the various subtags in the extension and thus MAY define an alternate canonicalization scheme for the extension's subtags. Extensions MAY define how the order of the extension's subtags are interpreted. For example, an extension could define that its subtags are in canonical order when the subtags are placed into ASCII order: that is, "en-a-aaa-bbb-ccc" instead of "en-a-ccc-bbb-aaa". Another extension might define that the order of the subtags influences their semantic meaning (so that "en-b-ccc-bbb-aaa" has a different value from "en-b-aaa-bbb-ccc"). However, extension specifications SHOULD be designed so that they are tolerant of the typical processes described in Section 3.7 (Extensions and the Extensions Registry).
Private use subtags, like all other subtags, MUST conform to the format and content constraints in the ABNF. Private use subtags have no meaning outside the private agreement between the parties that intend to use or exchange language tags that employ them. The same subtags MAY be used with a different meaning under a separate private agreement. They SHOULD NOT be used where alternatives exist and SHOULD NOT be used in content or protocols intended for general use.
Private use subtags are simply useless for information exchange without prior arrangement. The value and semantic meaning of private use tags and of the subtags used within such a language tag are not defined by this document.
Private use sequences introduced by the 'x' singleton are completely opaque to users or implementations outside of the private use agreement. So, in addition to private use subtag sequences introduced by the singleton subtag 'x', the Language Subtag Registry provides private use language, script, and region subtags derived from the private use codes assigned by the underlying standards. These subtags are valid for use in forming language tags; they are RECOMMENDED over the 'x' singleton private use subtag sequences because they convey more information via their linkage to the language tag's inherent structure.
For example, the region subtags 'AA', 'ZZ', and in the ranges 'QM'-'QZ' and 'XA'-'XZ' (derived from the ISO 3166-1 private use codes) can be used to form a language tag. A tag such as "zh-Hans-XQ" conveys a great deal of public, interchangeable information about the language material (that it is Chinese in the simplified Chinese script and is suitable for some geographic region 'XQ'). While the precise geographic region is not known outside of private agreement, the tag conveys far more information than an opaque tag such as "x-somelang" or even "zh-Hans-x-xq" (where the 'xq' subtag's meaning is entirely opaque).
However, in some cases content tagged with private use subtags can interact with other systems in a different and possibly unsuitable manner compared to tags that use opaque, privately defined subtags, so the choice of the best approach sometimes depends on the particular domain in question.
This section deals with the processes and requirements necessary for IANA to undertake to maintain the subtag and extension registries as defined by this document and in accordance with the requirements of [RFC5226] (Narten, T. and H. Alvestrand, “Guidelines for Writing an IANA Considerations Section in RFCs,” May 2008.).
The impact on the IANA maintainers of the two registries defined by this document will be a small increase in the frequency of new entries or updates. IANA also is required to create a new mailing list (described below in Section 5.1 (Language Subtag Registry)) to announce registry changes and updates.
Upon adoption of this document, IANA will update the registry using instructions and content provided in a companion document: [draft‑4645bis] (Ewell, D., Ed., “Update to the Language Subtag Registry,” May 2009.). The criteria and process for selecting the updated set of records are described in that document. The updated set of records represents no impact on IANA, since the work to create it will be performed externally.
Future work on the Language Subtag Registry includes the following activities:
Each registration form sent to IANA contains a single record for incorporation into the registry. The form will be sent to "email@example.com" by the Language Subtag Reviewer. It will have a subject line indicating whether the enclosed form represents an insertion of a new record (indicated by the word "INSERT" in the subject line) or a replacement of an existing record (indicated by the word "MODIFY" in the subject line). At no time can a record be deleted from the registry.
IANA will extract the record from the form and place the inserted or modified record into the appropriate section of the language subtag registry, grouping the records by their 'Type' field. Inserted records can be placed anywhere within the appropriate section; there is no guarantee that the registry's records will be placed in any particular order except that they will always be grouped by 'Type.' Modified records overwrite the record they replace.
Whenever an entry is created or modified in the registry, the 'File-Date' record at the start of the registry is updated to reflect the most recent modification date in the [RFC3339] (Klyne, G., Ed. and C. Newman, “Date and Time on the Internet: Timestamps,” July 2002.) "full-date" format: included in any request to insert or modify records will be a new File-Date record indicating the acceptance date of the record. This record is to be placed first in the registry, replacing the existing File-Date record. In the event that the File-Date record present in the registry has a later date than the record being inserted or modified, then the latest (most recent) record will be preserved. IANA should attempt to process multiple registration requests in order according to the File-Date in the form, since one registration could otherwise cause a more recent change to be overwritten.
The updated registry file MUST use the UTF-8 character encoding and IANA MUST check the registry file for proper encoding. Non-ASCII characters can be sent to IANA by attaching the registration form to the email message or by using various encodings in the mail message body (UTF-8 is recommended). IANA will verify any unclear or corrupted characters with the Language Subtag Reviewer prior to posting the updated registry.
IANA will also archive and make publicly available from "http://www.iana.org/assignments/lang-subtags-templates/" each registration form. Note that multiple registrations can pertain to the same record in the registry.
Developers who are dependent upon the language subtag registry sometimes would like to be informed of changes in the registry so that they can update their implementations. When any change is made to the language subtag registry, IANA will send an announcement message to "firstname.lastname@example.org" (a self-subscribing list that only IANA can post to).
The Language Tag Extensions Registry can contain at most 35 records and thus changes to this registry are expected to be very infrequent.
Future work by IANA on the Language Tag Extensions Registry is limited to two cases. First, the IESG MAY request that new records be inserted into this registry from time to time. These requests MUST include the record to insert in the exact format described in Section 3.7 (Extensions and the Extensions Registry). In addition, there MAY be occasional requests from the maintaining authority for a specific extension to update the contact information or URLs in the record. These requests MUST include the complete, updated record. IANA is not responsible for validating the information provided, only that it is properly formatted. IANA SHOULD take reasonable steps to ascertain that the request comes from the maintaining authority named in the record present in the registry.
Language tags used in content negotiation, like any other information exchanged on the Internet, might be a source of concern because they might be used to infer the nationality of the sender, and thus identify potential targets for surveillance.
This is a special case of the general problem that anything sent is visible to the receiving party and possibly to third parties as well. It is useful to be aware that such concerns can exist in some cases.
The evaluation of the exact magnitude of the threat, and any possible countermeasures, is left to each application protocol (see BCP 72 (Rescorla, E. and B. Korver, “Guidelines for Writing RFC Text on Security Considerations,” July 2003.) [RFC3552] for best current practice guidance on security threats and defenses).
The language tag associated with a particular information item is of no consequence whatsoever in determining whether that content might contain possible homographs. The fact that a text is tagged as being in one language or using a particular script subtag provides no assurance whatsoever that it does not contain characters from scripts other than the one(s) associated with or specified by that language tag.
Since there is no limit to the number of variant, private use, and extension subtags, and consequently no limit on the possible length of a tag, implementations need to guard against buffer overflow attacks. See Section 4.4 (Length Considerations) for details on language tag truncation, which can occur as a consequence of defenses against buffer overflow.
Although the specification of valid subtags for an extension (see Section 3.7 (Extensions and the Extensions Registry)) MUST be available over the Internet, implementations SHOULD NOT mechanically depend on it being always accessible, to prevent denial-of-service attacks.
The syntax in this document requires that language tags use only the characters A-Z, a-z, 0-9, and HYPHEN-MINUS, which are present in most character sets, so the composition of language tags shouldn't have any character set issues.
The rendering of text based on the language tag is not addressed here. Historically, some processes have relied on the use of character set/encoding information (or other external information) in order to infer how a specific string of characters should be rendered. Notably this applies to language- and culture-specific variations of Han ideographs as used in Japanese, Chinese, and Korean, where use of, for example, a Japanese character encoding such as EUC-JP implies that the text itself is in Japanese. When language tags are applied to spans of text, rendering engines might be able to use that information to better select fonts or make other rendering choices, particularly where languages with distinct writing traditions use the same characters.
The main goal for this revision of this document was to incorporate two new parts of ISO 639 (ISO 639-3 and ISO 639-5) and their attendant sets of language codes into the IANA Language Subtag Registry. This permits the identification of many more languages and language collections than previously supported.
The specific changes in this document to meet these goals are:
|[ISO15924]||International Organization for Standardization, “ISO 15924:2004. Information and documentation -- Codes for the representation of names of scripts,” January 2004.|
|[ISO3166-1]||International Organization for Standardization, “ISO 3166-1:2006. Codes for the representation of names of countries and their subdivisions -- Part 1: Country codes,” November 2006.|
|[ISO639-1]||International Organization for Standardization, “ISO 639-1:2002. Codes for the representation of names of languages -- Part 1: Alpha-2 code,” July 2002.|
|[ISO639-2]||International Organization for Standardization, “ISO 639-2:1998. Codes for the representation of names of languages -- Part 2: Alpha-3 code,” October 1998.|
|[ISO639-3]||International Organization for Standardization, “ISO 639-3:2007. Codes for the representation of names of languages - Part 3: Alpha-3 code for comprehensive coverage of languages,” February 2007.|
|[ISO639-5]||International Organization for Standardization, “ISO 639-5:2008. Codes for the representation of names of languages -- Part 5: Alpha-3 code for language families and groups,” May 2008.|
|[ISO646]||International Organization for Standardization, “ISO/IEC 646:1991, Information technology -- ISO 7-bit coded character set for information interchange.,” 1991.|
|[RFC2026]||Bradner, S., “The Internet Standards Process -- Revision 3,” BCP 9, RFC 2026, October 1996 (TXT).|
|[RFC2028]||Hovey, R. and S. Bradner, “The Organizations Involved in the IETF Standards Process,” BCP 11, RFC 2028, October 1996 (TXT, HTML, XML).|
|[RFC2119]||Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” BCP 14, RFC 2119, March 1997 (TXT, HTML, XML).|
|[RFC2277]||Alvestrand, H., “IETF Policy on Character Sets and Languages,” BCP 18, RFC 2277, January 1998 (TXT, HTML, XML).|
|[RFC3339]||Klyne, G., Ed. and C. Newman, “Date and Time on the Internet: Timestamps,” RFC 3339, July 2002 (TXT, HTML, XML).|
|[RFC4647]||Phillips, A. and M. Davis, “Matching of Language Tags,” BCP 47, RFC 4647, September 2006 (TXT).|
|[RFC5226]||Narten, T. and H. Alvestrand, “Guidelines for Writing an IANA Considerations Section in RFCs,” BCP 26, RFC 5226, May 2008 (TXT).|
|[RFC5234]||Crocker, D. and P. Overell, “Augmented BNF for Syntax Specifications: ABNF,” STD 68, RFC 5234, January 2008 (TXT).|
|[UAX14]||Freitag, A., “Unicode Standard Annex #14: Line Breaking Properties,” August 2006.|
|[UN_M.49]||Statistics Division, United Nations, “Standard Country or Area Codes for Statistical Use,” Revision 4 (United Nations publication, Sales No. 98.XVII.9, June 1999.|
|[RFC1766]||Alvestrand, H., “Tags for the Identification of Languages,” RFC 1766, March 1995 (TXT).|
|[RFC2046]||Freed, N. and N. Borenstein, “Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types,” RFC 2046, November 1996 (TXT).|
|[RFC2047]||Moore, K., “MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text,” RFC 2047, November 1996 (TXT, HTML, XML).|
|[RFC2231]||Freed, N. and K. Moore, “MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations,” RFC 2231, November 1997 (TXT, HTML, XML).|
|[RFC2781]||Hoffman, P. and F. Yergeau, “UTF-16, an encoding of ISO 10646,” RFC 2781, February 2000 (TXT).|
|[RFC2860]||Carpenter, B., Baker, F., and M. Roberts, “Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority,” RFC 2860, June 2000 (TXT).|
|[RFC3066]||Alvestrand, H., “Tags for the Identification of Languages,” RFC 3066, January 2001 (TXT).|
|[RFC3282]||Alvestrand, H., “Content Language Headers,” RFC 3282, May 2002 (TXT).|
|[RFC3552]||Rescorla, E. and B. Korver, “Guidelines for Writing RFC Text on Security Considerations,” BCP 72, RFC 3552, July 2003 (TXT).|
|[RFC3629]||Yergeau, F., “UTF-8, a transformation format of ISO 10646,” STD 63, RFC 3629, November 2003 (TXT).|
|[RFC4645]||Ewell, D., “Initial Language Subtag Registry,” RFC 4645, September 2006 (TXT).|
|[RFC4646]||Phillips, A. and M. Davis, “Tags for Identifying Languages,” BCP 47, RFC 4646, September 2006 (TXT).|
|[UTS35]||Davis, M., “Unicode Technical Standard #35: Locale Data Markup Language (LDML),” December 2007.|
|[Unicode]||Unicode Consortium, “The Unicode Consortium. The Unicode Standard, Version 5.0, (Boston, MA, Addison-Wesley, 2003. ISBN 0-321-49081-0),” January 2007.|
|[draft-4645bis]||Ewell, D., Ed., “Update to the Language Subtag Registry,” May 2009.|
|[iso639.prin]||ISO 639 Joint Advisory Committee, “ISO 639 Joint Advisory Committee: Working principles for ISO 639 maintenance,” March 2000.|
|[record-jar]||Raymond, E., “The Art of Unix Programming,” 2003.|
Any list of contributors is bound to be incomplete; please regard the following as only a selection from the group of people who have contributed to make this document what it is today.
The contributors to RFC 4646, RFC 4647, RFC 3066, and RFC 1766, the precursors of this document, made enormous contributions directly or indirectly to this document and are generally responsible for the success of language tags.
The following people contributed to this document:
Stephane Bortzmeyer, Karen Broome, Peter Constable, John Cowan, Martin Duerst, Frank Ellerman, Doug Ewell, Deborah Garside, Marion Gunn, Alfred Hoenes, Kent Karlsson, Chris Newman, Randy Presuhn, Stephen Silver, Shawn Steele, and many, many others.
Very special thanks must go to Harald Tveit Alvestrand, who originated RFCs 1766 and 3066, and without whom this document would not have been possible.
Special thanks go to Michael Everson, who served as the Language Tag Reviewer for almost the entire RFC 1766/RFC 3066 period, as well as the Language Subtag Reviewer since the adoption of RFC 4646.
Special thanks also to Doug Ewell, for his production of the first complete subtag registry, his work to support and maintain new registrations, and his careful editorship of both RFC 4645 and [draft‑4645bis] (Ewell, D., Ed., “Update to the Language Subtag Registry,” May 2009.).
Simple language subtag:
- de (German)
- fr (French)
- ja (Japanese)
- i-enochian (example of a grandfathered tag)
Language subtag plus Script subtag:
- zh-Hant (Chinese written using the Traditional Chinese script)
- zh-Hans (Chinese written using the Simplified Chinese script)
- sr-Cyrl (Serbian written using the Cyrillic script)
- sr-Latn (Serbian written using the Latin script)
Extended language subtags and their primary language subtag counterparts:
zh-cmn-Hans-CN (Chinese, Mandarin, Simplified script, as used in China)
cmn-Hans-CN (Mandarin Chinese, Simplified script, as used in China)
zh-yue-HK (Chinese, Cantonese, as used in Hong Kong SAR)
yue-HK (Cantonese Chinese, as used in Hong Kong SAR)
- zh-Hans-CN (Chinese written using the Simplified script as used in mainland China)
- sr-Latn-RS (Serbian written using the Latin script as used in Serbia)
sl-rozaj (Resian dialect of Slovenian)
sl-rozaj-biske (San Giorgio dialect of Resian dialect of Slovenian)
sl-nedis (Nadiza dialect of Slovenian)
de-CH-1901 (German as used in Switzerland using the 1901 variant [orthography])
sl-IT-nedis (Slovenian as used in Italy, Nadiza dialect)
- hy-Latn-IT-arevela (Eastern Armenian written in Latin script, as used in Italy)
- de-DE (German for Germany)
- en-US (English as used in the United States)
- es-419 (Spanish appropriate for the Latin America and Caribbean region using the UN region code)
Private use subtags:
Private use registry values:
- x-whatever (private use using the singleton 'x')
- qaa-Qaaa-QM-x-southern (all private tags)
- de-Qaaa (German, with a private script)
- sr-Latn-QM (Serbian, Latin-script, private region)
- sr-Qaaa-RS (Serbian, private script, for Serbia)
Tags that use extensions (examples ONLY: extensions MUST be defined by revision or update to this document or by RFC):
Some Invalid Tags:
- de-419-DE (two region tags)
- a-DE (use of a single-character subtag in primary position; note that there are a few grandfathered tags that start with "i-" that are valid)
- ar-a-aaa-b-bbb-a-ccc (two extensions with same single-letter prefix)
LANGUAGE SUBTAG REGISTRATION FORM 1. Name of requester: Han Steenwijk 2. E-mail address of requester: han.steenwijk @ unipd.it 3. Record Requested: Type: variant Subtag: biske Description: The San Giorgio dialect of Resian Description: The Bila dialect of Resian Prefix: sl-rozaj Comments: The dialect of San Giorgio/Bila is one of the four major local dialects of Resian 4. Intended meaning of the subtag: The local variety of Resian as spoken in San Giorgio/Bila 5. Reference to published description of the language (book or article): -- Jan I.N. Baudouin de Courtenay - Opyt fonetiki rez'janskich govorov, Varsava - Peterburg: Vende - Kozancikov, 1875.
LANGUAGE SUBTAG REGISTRATION FORM 1. Name of requester: Jaska Zedlik 2. E-mail address of requester: jz53 @ zedlik.com 3. Record Requested: Type: variant Subtag: tarask Description: Belarusian in Taraskievica orthography Prefix: be Comments: The subtag represents Branislau Taraskievic's Belarusian orthography as published in "Bielaruski klasycny pravapis" by Juras Buslakou, Vincuk Viacorka, Zmicier Sanko, and Zmicier Sauka (Vilnia-Miensk 2005). 4. Intended meaning of the subtag: The subtag is intended to represent the Belarusian orthography as published in "Bielaruski klasycny pravapis" by Juras Buslakou, Vincuk Viacorka, Zmicier Sanko, and Zmicier Sauka (Vilnia-Miensk 2005). 5. Reference to published description of the language (book or article): Taraskievic, Branislau. Bielaruskaja gramatyka dla skol. Vilnia: Vyd. "Bielaruskaha kamitetu", 1929, 5th edition. Buslakou, Juras; Viacorka, Vincuk; Sanko, Zmicier; Sauka, Zmicier. Bielaruski klasycny pravapis. Vilnia-Miensk, 2005. 6. Any other relevant information: Belarusian in Taraskievica orthography became widely used, especially in Belarusian-speaking Internet segment, but besides this some books and newspapers are also printed using this orthography of Belarusian.
|Addison Phillips (editor)|
|Mark Davis (editor)|