Getting Started

Creating Translation Packages

We recommend that you normally use professional translators for the bulk of your translations, and while you can also have licenses for translators to let them do their work inside Paligo, agencies often prefer to use their own familiar tools ("translation memories").

To support this, Paligo can easily create a translation package, perfectly suited for any translation provider, by using a standardized XML format for translations - XLIFF.

When you create a translation package in Paligo, any previously translated text fragments are automatically included and marked as already translated, and the translator can easily import all these translations into their system, at the click of a button. This way all translations are utilized and you do not have to pay for re-translating segments.

  1. In the Translation View, open the Tool menu in the top right corner, and select Export translation.

  2. In the dialog that opens, select languages for the translation package, select the format (normally XLIFF, the default value, although you can also export to MemSource if you have the integration), and then Export.


    Note that you have several format options, another XLIFF format and PO. The variant XLIFF format is preferred by some translation tools, and PO is mostly used for translation of web content. But the default XLIFF choice is the most common.

  3. Choose whether you want to include previously translated content or not.

    If you have previously translated and approved content, you can include that. It will then be marked as "final", and assuming the translation vendor has the correct settings in their translation software, these segments will be skipped.

    You can also choose to include translations that are there, but not approved.


    Translation software will often segment content differently than a full paragraph element for instance. Sometimes you may then want to uncheck these boxes, at least the "fuzzy" option, so that the translation software segmentation can match on that level.

  4. Save the file. Then send it to your translator to open and translate. All previously translated special segments will be skipped by their translation tool.

  5. When you get the fully translated file back, upload the package back into Paligo, by selecting the option Upload translation file from the same menu in the top right corner.

  6. Review and edit the translation in the Translation View if needed, and mark the translation complete (either for individual translation segments, if you are post-editing the translation, or for the entire publication in the top right menu). The publication and all its topics have been translated and stored in the system.


    Marking the translation as complete is important.

    Only at that point will the translations be marked as final and approved, meaning the next time you send a translation containing the same topics or text fragments, the translation provider's software will simply skip those segments.

  7. If this was part of an assignment workflow, also click the button Your assignments and mark it as Done.

Search results