Intl object is the namespace for the ECMAScript Internationalization API, which provides language sensitive string comparison, number formatting, and date and time formatting. The constructors for
DateTimeFormat objects are properties of the
Intl object. This page documents these properties as well as functionality common to the internationalization constructors and other language sensitive functions.
- Constructor for collators, objects that enable language sensitive string comparison.
- Constructor for objects that enable language sensitive date and time formatting.
- Constructor for objects that enable language sensitive number formatting.
Locale identification and negotiation
The internationalization constructors as well as several language sensitive methods of other constructors (listed under See also) use a common pattern for identifying locales and determing the one they will actually use: They all accept
options arguments, and negotiate the requested locale(s) against the locales they support using an algorithm specified in the
locales argument must be either a string holding a BCP 47 language tag, or an array of such language tags. If the locales argument is not provided or is undefined, the runtime's default locale is used.
A BCP 47 language tag identifies a language or locale (the difference between the two is fuzzy). In their most common form it can contain, in this order: A language code, a script code, and a country code, all separated by hyphens. Examples:
- "hi": Hindi.
- "de-AT": German as used in Austria.
- "zh-Hans-CN": Chinese written in simplified characters as used in China.
The subtags identifying languages, scripts, countries (regions), and (rarely used) variants in BCP 47 language tags can be found in the IANA Language Subtag Registry.
DateTimeFormat object. Examples:
- "de-DE-u-co-phonebk": Use the phonebook variant of the German sort order, which expands umlauted vowels to character pairs: ä → ae, ö → oe, ü → ue.
- "th-TH-u-nu-thai": Use Thai digits (๐, ๑, ๒, ๓, ๔, ๕, ๖, ๗, ๘, ๙) in number formatting.
- "ja-JP-u-ca-japanese": Use the Japanese calendar in date and time formatting, so that 2013 is expressed as the year 25 of the Heisei period, or 平成25.
locales argument, after stripping off all Unicode extensions, is interpreted as a prioritized request from the application. The runtime compares it against the locales it has available and picks the best one available. Two matching algorithms exist: The "lookup" matcher follows the Lookup algorithm specified in BCP 47; the "best fit" matcher lets the runtime provide a locale that's at least, but possibly more, suited for the request than the result of the Lookup algorithm. If the application doesn't provide a
locales argument, or the runtime doesn't have a locale that matches the request, then the runtime's default locale is used. The matcher can be selected using a property of the options argument (see below).
If the selected language tag had a Unicode extension substring, that extension is now used to customize the constructed object or the behavior of the function. Each constructor or function supports only a subset of the keys defined for the Unicode extension, and the supported values often depend on the language tag. For example, the "co" key (collation) is only supported by
Collator, and its "phonebk" value is only supported for German.
options argument must be an object with properties that vary between constructors and functions. If the
options argument is not provided or is undefined, default values are used for all properties.
One property is supported by all language sensitive constructors and functions: The
localeMatcher property, whose value must be a string
"best fit" and which selects one of the locale matching algorithms described above.
|ECMAScript Internationalization API Specification 1st Edition (ECMA-402)||Standard||Initial definition.|
|Feature||Chrome||Firefox (Gecko)||Internet Explorer||Opera||Safari (WebKit)|
|Basic support||24||29 (29)||11||15||Not supported|
|Feature||Android||Chrome for Android||Firefox Mobile (Gecko)||IE Phone||Opera Mobile||Safari Mobile|
|Basic support||Not supported||26||Not supported
|Not supported||Not supported||Not supported|