Other Projects

Mozilla accounts

Localization PM is automatically set as reviewer via CODEOWNER for pull requests affecting Fluent files.

Additional automation flags PMs for gettext files.

Enabling a new locale for localization

To enable a new locale for localization, two steps must be taken.

Step 1: The locale needs to be enabled in Pontoon via the admin interface. This will create the respective locale folder in the L10n repository.

Step 2: For gettext files, you will need to add a LC_MESSAGES folder and the client.po and server.po files manually into the generated locale folder in the L10n repository (these files may be initially empty).

Automation: Strings export

Strings from the fxa repository are stored in multiple .ftl files across multiple folders (in the case of Fluent) and stored within .mustache and JavaScript files (in the case of gettext). Automation extracts and merges content into project files.

Enabling a locale for production

Mozilla accounts has a required completion level of 70% for being enabled in production. Past tickets for updating locales are tracked in JIRA. To enable a locale in production, a PR can be made to the fxa repository adding the locale to the supported-languages.json file.

Mozilla Monitor

To add a new locale to this project it’s enough to add the locale to Pontoon. This will make the locale automatically available on the dev server and commit to the repository.

Localization PM is automatically set as reviewer via CODEOWNER for pull requests affecting Fluent files.

For information on the automation, see the README in the l10n repository.

Mozilla VPN Client

To add a new locale to this project it’s enough to add the locale to Pontoon. The locale will be added automatically to Nightly builds, but will be available in production builds only after it reaches 70% completion (and dropped automatically if it gets lower).

Builds are created via GitHub automation and available as assets in each run of GitHub Actions. Builds are multilocale, and users can switch language directly from the app settings.

For this project, there are several elements of automation running (linter, string extraction).

Automation: Strings export

Strings are stored in the original repository either directly in the code or in YAML format.

Automation exports strings from the main branch and all releases branches into a single XLIFF file, and creates a pull request every workday at 7 AM UTC updating all XLIFF files in the repository. The PM in charge is automatically set as reviewer via CODEOWNER.

Automation: Linting

There is a linter running in the code repository, checking for common mistakes in strings:

  • Use of straight quotes ' or " instead of ' or “”.
  • Use of ... instead of ….
  • Lack of comments when the string has placeables.
  • Empty strings.