What's localized in Persona
When a user tries to sign into a website using Persona, they are guided through the process of signing up or signing in.
If they haven't signed in using Persona before, this involves choosing a new password and an email address to use, then proving ownership of that email address. If the email address they want to use is already known to Persona, this may involve them entering a password or simply selecting that email address.
In the future, the user interface for all this is will be integrated into the browser, and localized along with the browser's own localization. Until then, the user interface consists of a series of dialogs served from
https://login.persona.org/, via the website's inclusion of
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
- For each language tag in the
- 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|
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