Localization Process

Overview

The following document gives a step by step guide for the string localization process, meaning the import and the export of strings and their translations in our project. For documentation on how to add strings in the repo, please look into the related wiki page.

Important note

Be aware that manual string import and export shouldn't be done anymore. They both need to happen through Github actions.

Github action import process

Import

String import from the firefoxios-l10n repository happens once a week and points to the main branch. The Github action opens a PR, which then needs to be reviewed and merged by the developer team. Importing strings can also be done by pointing to a certain branch. For example, on hard freeze a string import can be triggered by running the Create a PR with changes after importing strings workflow, and writing down the targeted version of the branch as shown in following picture:

Export

String export happens by adding new strings into the Firefox for iOS strings file. Any developer adding new strings to the project should be familiar with the principles described in l10n documentation.

Steps to add strings to the strings.swift file:

1. Add the new strings in the related struct. If there's no struct for a string, create one related to the feature or section this string will be under.
2. How to define a localized string can be found here.
3. Once all strings are added, open a PR on Firefox for iOS.
4. Once merged, the new strings will be exported automatically to the firefox l10n repository through the automated Github action. In case the export needs to be triggered sooner, ping Delphine so the export Github action can be triggered.