Iso code es

The registry is a text file in a special, machine-readable, format called "record-jar". Each subtag has its own record, consisting of several lines of text, which identifies the subtags, their use, and some information useful in selecting which subtags are right for specific circumstances. Each record contains the subtag itself, its type "language", in this case , a description or set of descriptions , and the date that the record was added to the registry. All of the initial records have the date "" as shown above.

Additional information is sometimes available. For example, in the record for the Czech language cs above, you'll notice a field called "Suppress-Script". This field indicates that most texts in Czech are written in the Latin script and that the "Latn" script code is inappropriate for most language tags identifying content in Czech.

That is, a tag like "cs-CZ" is recommended, while a tag such as "cs-Latn-CZ" is strongly discouraged. Other fields that can appear include a "Deprecated" field that shows a date on which a particular code was deprecated. This almost always appears with another field called "Preferred-Value", which indicates a more appropriate subtag to use for that value.

For example, the code "TP" was deprecated by ISO when that country changed its administration and name in The registration process can still be used to add information to or update information about specific records, as well as adding entire new subtags. Records cannot be removed and there are rules to prevent the meaning of a subtag from being "mutated" to mean something completely different.

The file itself contains a "File-Date" record, showing the last time the registry was updated. Combined with the various date fields in the records themselves, it is possible to validate any particular tag or its subtags for any given date, past or present. RFC bis actually consists of three parts.

First, there is the document that describes the syntax of language tags and the registry, as well as how language tags are maintained and so forth. This document is an Internet-Draft called "draft-ietf-ltru-registry" and is about 62 pages long. This document was edited and maintained by Doug Ewell. The last piece of the puzzle is an Internet-Draft on matching of language tags.

This document was being worked on at the time this was written and its current name is "draft-ietf-ltru-matching". The IETF website hosts all of these documents, or you can find the latest versions of them all listed on my personal website and on the W3C site.

Matching, as noted earlier, is fairly well understood in its simplest, "prefix matching" form, which is described above in the section on scripts. However, there are some intriguing applications for RFC bis style tags in matching, as well as some well-known matching schemes that were not well documented in RFC This work is, at the time of writing, awaiting completion of the Last Call process.

Despite the changes in how language tags are formed and maintained, a few cases remain which the new design does not fully address. A notable problem is that of identifying variations of a language or within family of languages. While variant or region subtags are often useful for this purpose, some languages exhibit long-lived, stable, well-described variations that are not particularly well-described by national boundaries.

In addition, ISO has occasionally assigned codes to "macro-languages", which are language families that contain a number of recognizably related but not necessarily mutually intelligible languages. An excellent example is once again Chinese. The ISO code 'zh' identifies "Chinese", but the concept of Chinese encloses a number of distinct languages or dialects that share certain traits.

While these languages are written very similarly making tags such as "zh-Hant" and "zh-Hans" useful , spoken content is very different indeed. And, again, the available regional options are poor proxies for the spoken dialects many of which are confined to mainland China.

RFC bis provides part of the solution to this conundrum by reserving space for yet another kind of specialized subtag, called an "extended language subtag". These are three-letter codes that follow the primary language subtag but occur before the script subtag. There are very clear rules for when one of these subtags can be used they must be used only with the specified prefix , and it is anticipated that a very small revision to RFC bis will take place in mid to make these available.

The reason for the delay is that the basis for defining the extended language subtags is expected to be ISO ISO also defines which languages are enclosed by which Macro Languages. Thus Mandarin Chinese a spoken variation will be identified by the ISO code 'cmn' and rules will require that code, when used as a subtag, to always appear with its macrolanguage "zh" Chinese. This will finally make is possible to tag Chinese content accurately in all dimensions:.

There are about forty different languages other than Chinese that are defined as Macro Languages in the prototype for ISO Most of these are minority languages and it is possible that the ability to accurately identify these language variations in content may have an impact on their preservation amongst the living languages. In any case, extended language subtags are already fully specified and are merely waiting for ISO to finally be official and complete before being included in the list of language subtags.

Note that implementers merely need to update their copy of the registry when ISO is added, as long as they have followed the implementation requirements already in RFC bis. The new version of BCP 47 provides the ability to accurately tag or request content using stable, well-defined tags. These tags address a number of long standing problems with language identification, leading, hopefully, to richer language-aware features in our software and better support for language in our documents.

Understanding these tags and their format will help users adopt them and use them wisely and consistently. Looking to get certified? Media kit. Zoom in on standards We've created some ISO-themed backgrounds for your video calls to transport you out of your home and immerse you in the dazzling world of standards.

When things don't work as they should, it often means that standards are absent. ISO Quality management systems. The ISO family is the world's most best-known quality management standard for companies and organizations of any size.

ISO Environmental management systems. Store Are you looking to buy International Standards, guidelines, collections and checklists? Knowing the European country code can make the relevant numbers a breeze to find. While only the codes for Europe are covered here, these country code abbreviations are designated for every continent. For every country or partial country that is recognized in Europe, there is a code. The most recognized country code is just two letters, but there are other codes available.

These organization abbreviations actually create a new word. Staff Writer. All rights reserved. European Union Country two letter codes. The two-letter codes ISO alpha-2 abbreviate the country name into two easy-to-identify letters.