i18n
Functions to internationalize your extension. You can use these APIs to get localized strings from locale files packaged with your extension, find out the browser's current language, and find out the value of its Accept-Language header.
See the Internationalization page for a guide on using this API.
Browser compatibility
|
Desktop |
Mobile |
|
Chrome |
Edge |
Firefox |
Internet Explorer |
Opera |
Safari |
WebView Android |
Chrome Android |
Firefox for Android |
Opera Android |
Safari on IOS |
Samsung Internet |
LanguageCode |
47 |
14 |
45 |
? |
34 |
No |
? |
? |
48 |
? |
No |
? |
detectLanguage |
47 |
79 |
47 |
? |
34 |
No |
? |
? |
106
48–106The method existed but always threw an error.
|
? |
No |
? |
getAcceptLanguages |
47 |
14 |
47 |
? |
34 |
14 |
? |
? |
48 |
? |
15 |
? |
getMessage |
17 |
14["Throws an exception instead returning an empty string if the message does not exist.", "Expects substitutions to be strings, while other browsers allow any value which is then converted to a string."]
|
45Firefox 47 and earlier returns "??" instead of "" if the message is not found in _locales, bug 1258199 changed this act to match Chrome, landed on Firefox 48.
|
? |
15 |
14 |
? |
? |
48 |
? |
15 |
? |
getUILanguage |
35 |
14 |
47Firefox 55 and earlier returns a language tag that's separated with the underscore character instead of hyphen, see bug 1374552.
|
? |
Yes |
14 |
? |
? |
48 |
? |
15 |
? |
Example extensions
Note: This API is based on Chromium's chrome.i18n
API. This documentation is derived from i18n.json
in the Chromium code.