Mantenha um processo de localização ágil e evite atrasos na tradução de textos adicionados ou novos recursos do produto. Integrate your project branches with Crowdin and allow translators to access all new texts immediately.
Quando várias pessoas estão trabalhando no desenvolvimento de produtos, as ramificações ajudam a gerenciar diferentes versões do conteúdo. If you have a continuous project, you can add project branches to Crowdin and allow translators to translate the texts in parallel with development to avoid deployment delays.
The branch in Crowdin looks like a regular folder marked with a special icon and has specific behavior for duplicated strings.
Example of branch structure in the version control system (VCS) and Crowdin:
There are a few ways to add branches to Crowdin:
To create a branch via API, use the Add Branch method.
If you use CLI, you can add and delete version branches with dedicated commands. Alternatively, you can create version branches during the file upload.
Read more about Branch Management with CLI.
You can set a specific priority for each branch by clicking an arrow icon next to the needed branch. Then translators will see branches sorted according to their priority on the language page and in the Editor.
Branches might have the following priorities:
To set a priority for your branches, follow these steps:
Because branches are different versions of the same product feature, their localization content is usually duplicated. To help translators translate versions consistently and avoid additional translation costs, we have the Show within a version branch option that allows hiding duplicated strings only between versions. If your source files contain strings with apparent identifiers (keys), it’s better to use a strict version of this option. In other cases, feel free to use a regular one.
When this option is chosen, only the master strings first uploaded to the system should be translated. All duplicated strings will automatically gain translations from the master strings.
To make sure versions work smoothly for your Crowdin project, we recommend the following workflow:
A captura de tela abaixo mostra como o fluxo de trabalho funciona na prática. Todos os textos de Master, Branch 1 e Branch 2 são transferidos para o servidor de tradução imediatamente após aparecerem, mesmo que as ramificações não sejam mescladas com o ramo Master ainda.
Translations from all version branches are placed in one ZIP archive when downloaded through the web interface. Use the CLI or API to download the translations for each branch individually.
To download translations of the specified version branch with API, you can use the following API methods:
Download de traduções do ramo da versão especificada:
$ crowdin download -b branch_name
A ramificação Master conterá novos textos das ramificações Feature assim que elas forem mescladas. While synchronizing with Crowdin, texts in the Master branch are populated with translations from the appropriate branch.
After synchronizing the updated Master branch with Crowdin, you can remove the Feature branch from Crowdin. Todas as traduções armazenadas na ramificação Master permanecerá.
You can verify translations on production using only the Feature branch before changes are merged with your Master branch. Such test deployment allows you to quickly revert to the original Master branch version if needed.