If new to localizing strings for a project, this would be a typical and recommended workflow:
-
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.
-
-
Once new source translations or keys are added to a project, translators start working in order to translate the content into supported languages.
-
Invite internal team members to work on a project.
-
Order professional translations from external providers.
-
-
Download translations.
-
Download the translations from the application in the required format.
-
Download files via API or CLI.
-
-
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.
-
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:
If more complex and customized workflows are required, these can be constructed with Phrase Orchestrator.