Prepare Content for Translation
Whether you are working with a translation service or are going to translate your content internally, you will need to prepare your content before you send it to the translators. Ideally, you should prepare for translation at the start of your project, so that you can consider using translatable variables from the start. But they can be set up and applied retrospectively if needed.
Tip
If you have content that you want exclude from the translation, see Exclude Content from Translation.
The preparation steps are:
-
Activate Languages - This makes the languages available to use.
You may also need to add any missing languages or dialects to Paligo, see Create Additional Languages.
-
Add the languages to your publications and topics, see Add a Language to a Publication or Topic.
-
Upload image variants for different languages, see Translate Images. (Optional)
-
Set up translatable variables, see Translate Variables. (Optional)
-
Consider if you need to provide your translators with information about Translate Filters. (Optional)
Note
Steps 3 to 5 inclusive are optional. You only need to complete these steps if your content contains images that need different images in other languages, variables and filters, respectively.
If you have content that you do not want to be translated, you can set it to be translation disabled.
To exclude content you do not want to be translated:
-
Select the topic or component in the Content Manager.
Paligo opens the content in the Editor.
-
Select the content in the topic.
-
Select the
paraelement in Element Structure Menu and choose Disable element translation.
Note
The element is highlighted in yellow and is locked to prevent it from being translated. In the underlying XML, it is given the
xinfo:translate="no"attribute and value. -
Select Save.
