Working with a Translation Service

When You Start Working with a Translation Service

At the start of your translation project:

  1. Find out if you need to set up Paligo's translation software integrations. These are needed if your translators are using Memsource or Semantix.

    For instructions on how to set up the integrations, see:

    Note

    If your translation service uses Crowdin, the translation process works differently as it does not require translation packages. For details, see Translating with Crowdin.

  2. Provide your translation service with the Translation Software Settings.

  3. Read the Translation Service Workflow. That explains the process and has links to the various other resources you need, including information on how to:

    If you will need to update and publish the content in the source language while waiting for translations to complete, you will need to branch your content. You can learn about the process for updating content while waiting for translations in Update Content when Translation is Not Finished.

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.