Merge and Translate the Updates
You now need to get the updates translated so put the updated topics into the In Translation state. Depending on how you want to manage your content, there are several ways to approach the translation.
You could:
-
Continue to manage the original branch and each updated branch separately. In this case, you should send the first update branch for translation. We recommend waiting until the translation is completed and imported before you send the second branch for translation.
-
Merge your updated branches to keep the original version and one updated branch. You can then send the updated branch for translation.
-
Merge your updated branches into the original version. You can then send the original version for translation again, and this time the translators will only need to translate the updated content.
Caution
Do not merge the branches with the original version until the translation for the original version is complete and imported. If you do, it will cause the translation and content to be misaligned.
When the translations are ready, you can import them into Paligo and review them. When you import, Paligo matches the translation to the appropriate version. For example, if you sent an update branch for translation, Paligo will match the translation to the IDs of the topics in the update branch.
Tip
To learn how to merge branches, see What is Merging?.