Learn how to get your Paligo content translated into other languages. Export content to translation services or translate it inside Paligo.
Paligo has built-in features for supporting the translation of your content. These include integrations with professional translation software (Semantix and Phrase), built-in workflows and a translation editor and assignments. These features are designed to manage the various ways of translating your content.
When your content is ready for translation, the next steps will vary depending on how your content is being translated. While Paligo recommends that you Work with a Translation Service, in some situations, it makes sense to Working in Translation View instead. You will also need to Prepare Content for Translation.
If you need to activate more languages, see Language Management.
You should avoid using both approaches together. This is because if you use a translation service, they will most likely use software that has a translation memory.
This is a record of the content you have sent to them and the translations they provided. If you subsequently change the translation in Paligo, then the content in Paligo and the translation memory will no longer be in sync. This can cause confusion and avoidable costs, as content that is not synced may be translated again.
Paligo has its own built-in translation editor called Translation View that you can use to perform simpler translations without translation memory. The translations are stored in the Paligo database with the matching source content. If you have reused content, any translations for that content are also reused.
This is a relatively simple editor with editing features and auto-translate which uses Google Translate. Using auto-translate can be a useful starting point for your translators, but we do not recommend that you rely on it entirely for your translations. You also have to keep track of changes manually. So if you add new content or change existing content in the source language, you will need to remember to update the translations too. To find out more about the workflow and how to get started with this approach, see Workflow for Internal Translation.
If you are only making minor changes to the translation, such as fixing a typo or changing a product name, you could use both a translation service and Translation View, but it is a good idea to check this with your translation service first and you should only make minor changes that are unlikely to affect the translation overall. Because the content in Paligo and the translation memory will no longer be in sync. This can cause confusion and avoidable costs, as content that is not synced may be translated again.
If you are going to use Paligo for translating content inside your organization, see Work with Internal Translators.
Use the built-in translation editor if your organization is:
Unable to use an external translation service
Able to translate the content internally, without access to a professional translation software.
If you are going to use a translation service, an author can handle the translation export, see Work with a Translation Service. It is also possible to use a translation Integrate, such as Phrase, to export and import the content directly.
The following roles are able to handle translations: