Creating Translation Packages

Abstract

You can create translation packages to send to translation service providers. When the translation work is done, the translators return a translation package to you and you can import it into Paligo.

We recommend that you use professional translators for your translations. You can have licenses for translators to let them do their work inside Paligo, but agencies often prefer to use their own translation tools (often referred to as "translation memories").

If your translation company wants to use their own tool, you can use Paligo to create a translation package. The package uses a standardized XML format for translations, called XLIFF, and so is suitable for use with many translation tools.

The workflow for working with translation packages is:

  1. You export a translation file. This is a translation package and it automatically includes any previously translated text fragments and they are marked as already translated.

    Note

    If your content contains variables, you will also need to send the variable set for translation too. The variables need to be translatable variables, so you may need to convert your existing variables if they are of a different type. To find out more, see Translating Variables.

  2. You send the translation package to a translator. The translator uses translation software to work on the translations. They should apply the Translation Software Settings .

  3. The translator sends a translation package back to you. You can then import the translation package back into Paligo.

To create a translation package to send to a translator, you will export a translation. Then, when the translator sends you the translated content, you can import the translation back into Paligo.

  1. In the Content Manager, select the folder that contains the topic or publication that you want to translate. When you select the folder, Paligo shows the Resource View.

    Resource view showing a topic in the work in progress state.

    Note

    The Documents section at the top of the Content Manager is the top-level parent folder for all content. It is the parent folder for any content that is not in another folder.

  2. Use the status button to set the topic status to In Translation.

    Resource view showing a topic in the work in progress state. The state button is selected and it shows a menu containing other state options, including In Translation.
  3. Expand the entry for the publication or topic to see the details and then select the Translations tab.

    Resource view of a topic, with the topic set to In Translation. The Translation tab is selected, showing a list of translations, one per language, with a bar showing how complete those translations are.
  4. Select the options menu ( ... ) for a language you want to translate into. Then select Export translation to display the Export translation dialog.

    Export translation dialog, showing Translate from, Translate to, and Choose the document format settings.

    Tip

    Select Show incomplete topics to see a list of topics (in a publication) that are not fully translated.

    Resource view showing a selected language bar with the options menu on display. The show incomplete topics option is selected.
  5. On the Export translation dialog, use Translate to to choose the language(s) that you want to translate into.

    translate-to.jpg
  6. Choose the format. Typically, translators require the XLIFF format. But there are also other options, such as:

    • a variant XLIFF format that is required by some translation tools

    • PO, which is a format that is often used to translate web content

    • Memsource

    • Semantix

    document-format-translation.jpg
  7. Choose whether you want to include previously translated content. In most cases, we recommend that you Include approved translations, but do not include unapproved translations (also known as "fuzzy" translations).

    Export options section, showing checkboxes for "Include approved translations" and "Include fuzzy translations (not approved)"

    Checking the Include approved translations box tells Paligo to include any content that has already been translated and approved. The source and target language are included in the translation package. This content is then marked as "final". If the translation vendor has the appropriate settings in their translation software, this content will be imported into the translation memory system and will not be re-translated.

    Note

    You can include "fuzzy" translation target segments too. These are incomplete target segments, such as segments that have been translated before but where the source has changed since the last translation.

    However, in most cases, this is not recommended, as translation software will often segment content differently.

  8. Save the file. Paligo produces a .zip file that you can send to your translator.

  9. When you get the fully translated file back, upload the package back into Paligo. You can upload a .zip of multiple files or you can upload individual files. With a .zip, there is one file per language pair.

    To upload, either:

    • Display the publication or topic in Resource View, select the option menu ( ... ) and then select Import Translation.

    • Open the publication or topic in Translation View, select the cog icon and then select Import Translation.

    To access Translation View, find the topic or publication in the Content Manager and select it's options menu (... ). Then select Edit > Translate.

  10. Review and edit the translation in the Translation View.

    Translation view is split 50/50 on the screen, with an English page on the left and the translated German version on the right.

    Use the Translation View menu to mark the translation as complete. You can use the cog icon menu to mark the entire publication. Alternatively, you can select individual segments and mark them as complete.

    Cog menu selected on the Translate view. There are options for Translation is Complete and Translation is Not Complete.
    translation-menu-2.jpg

    To find out how to use the Translation View, see Using the Translation View.

    Note

    Marking the translation as complete is important.

    A translation needs to be marked as final and complete so that if it is included in a translation package again, it will not be re-translated. The translator's software can only skip past content that has been marked as final and complete.

  11. If the translation was part of an assignment workflow, select Your assignments and mark the translation as complete.

    Assignments option selected on Translation assignment. The menu shows various options, including Translation is Complete and Translation is Not Complete.

Note

We recommend that you use the Resource View for exporting translation files. But it is possible to use the Translation View instead. For that, find the topic or publication you want to translate in the Content Manager. Then select its options menu ( ... ) and choose Translate. In the Translation View, select the cog icon to access the options menu.

Cog menu for Translate View. Shows various options, including Export Translation.

Your translation provider is responsible for setting up their translation memory system (TMS). But they may need some guidance on what settings are appropriate for translating Paligo content.

Here, we provide some information about what settings to use and the intended workflow. We have used an example from the TMS "Memsource", but the same approach can be used for other TMSs, such as TRADOS, MemoQ, Swordfish, etc.

Example 1. XLIFF import settings
XLIFF 1.2 settings for translation software. Import note is checked. Save confirmed segments to TM on import is checked. Segment XLIFF is checked. Interpret linebreak/pagebreak tags is not checked. Preserve whitespaces is not checked. Copy source to empty target if segment is not imported is checked.

These settings (or similar in another TMS) will work for many use cases. Please note that:

  • The XLIFF is segmented according to the TMS rules (usually on sentence level)

  • Linebreaks and whitespaces are ignored

  • Previously translated and approved translations are imported into the translation memory.


Example 2. Status flag rules for import and export
Translation software settings for Import Segment Rules and Export Attributes Mapping

To get the most out of the translation, for example, to skip already translated segments, the TMS should:

  • Import approved as state=final

  • Export confirmed and locked segments as state=final.

  • Have non-locked content set to state=needs-review-translation, unless you do the review and approval process directly in a TMS. This will allow you to give final approval to the translation in Paligo.