Questa traduzione è incompleta. Collabora alla traduzione di questo articolo dall’originale in lingua inglese.
What's localized in Persona
In the future, the user interface for signing into sites with Persona will be directly integrated into the browser, and thus localized along with the browser's own localization. For browsers without integrated support, Persona's user interface consists of a series of dialogs served from login.persona.org. These dialogs are translated by a team of community volunteers, and more than 45 locales are currently enabled in production.
How Persona chooses localizations
The Persona service selects a language using the Accept-Language header sent alongside the browser's requests. The algorithm used to map an Accept-Language header to a language is the same as that used by mozilla.org:
- For each language tag in the
Accept-Languageheader:- check if we have an exact match for the language identified by the language tag
- check if we have an exact match for the language identified by the first part of the language tag
- If a match can't be made using rule (1), fall back to en-US. However, en or en-US is almost always the last accept-lang header sent by most browsers.
For example, the table below lists the language selected for various Accept-Language headers, if the following locales were supported: en-US, es, es-MX:
| Accept-Language Header | Selected language |
|---|---|
es-AR,es;q=0.8,en-us;q=0.5 |
es |
es-MX,es;q=0.8,en-us;q=0.5 |
es-MX |
es-es,en-us;q=0.5 |
en-US |
es-es |
en-US |
There is currently no way for a website to force the dialogs to appear in another language. This is because the Persona UI is logically (and in future native implementations will actually be) part of the browser UI, so its language should be consistent with the language selected for the browser.
How you can help
Persona uses Mozilla Verbatim to help volunteers create new translations. If you want to help out, read about getting started with Verbatim and check out the "BrowserID" project on Verbatim.