Translating

Localization Workflow (Strings)

If new to localizing strings for a project, this would be a typical and recommended workflow:

  1. Add new source translations and keys using one of these methods:

    • Use key management to add new keys to a project, along with a default translation.

    • Add keys via file upload (CLI).

    • Add keys via API.

  2. Once new source translations or keys are added to a project, translators start working in order to translate the content into supported languages.

  3. Download translations.

    • Download the translations from the application in the required format.

    • Download files via API or CLI.

  4. Merge conflicts

    No attempt to resolve merge conflicts is made but the most recent version of a translation is what is downloaded from a project. Avoid translating keys locally (outside of Phrase) to avoid merge conflicts and to ensure team members are accessing the most recent translations.

  5. Release new translations with the application.

    There is no need to have a connection to Phrase in a production environment. Calling APIs in production to retrieve localization data is not recommended.

    Treat received localization files like any other file in a code repository or project:

    1. Check them into version control.

    2. Run tests against the application (if available).

    3. Deploy and release the software normally.

Was this article helpful?

Sorry about that! In what way was it not helpful?

The article didn’t address my problem.
I couldn’t understand the article.
The feature doesn’t do what I need.
Other reason.

Note that feedback is provided anonymously so we aren't able to reply to questions.
If you'd like to ask a question, submit a request to our Support team.
Thank you for your feedback.