Resolving of translation configuration

In your translation BluePrint, you can configure items that contain source content for translation at a global level by configuring the Publication or, if you want finer-grained control over what content is translated and into what languages, you can configure Folders, Structure Groups and Categories. The translation configuration used is assigned.

You assign a 'translation configuration' to an item that contains content in a source language as follows:

  • SDL TMS—configure items by specifying a configuration ID (GUID) that specifies, amongst others, one or more Language Pairs consisting of a source language and target language. The source language of the Language Pairs dictate the language assigned to the Publication.
  • SDL WorldServer—configure items by specifying a Client (the organization or department using the translation services) and Project Type that specifies, amongst others, a source language (all other locales in the system are potential target languages). The Project Type language dictates the language assigned to the Publication.

Unconfigured items inherit the translation configuration from the nearest (in BluePrinting terms) item configured as a Source Publication. If Translation Manager cannot not find a translation configuration in Folder, Structure Group or Category, it will use the configuration at Publication level (if configured). If no Parent item is configured, an item cannot be sent for translation.

When you have configured source content, you can configure target content by configuring the target language. The possible target languages are displayed in a drop-down list which are derived from the translation configuration:

  • in SDL TMS, the languages are derived from the language pairs defined in the GUID.
  • in SDL WorldServer the languages are derived from the defined locales.

When performing a push translation, for example on a Component in a nested Folder, the Translation Manager walks up the Folder structure and uses the nearest translation configuration. If it does not find a translation configuration at Folder level, it will use the configuration at Publication level (if configured). When performing a push translation on a Page in a nested Structure Group, the Translation Manager will similarly walk up the Structure Groups and use the nearest translation configuration and use this configuration for the Page and the Components on the Page.

When performing a pull translation, for example on a Page in a nested Structure Group, the Translation Manager will create separate Translation Jobs for Pages and Components:
  • for the Page, it will walk up the Structure Groups and uses the nearest translation configuration.
  • for the Components, it will walk up the Folder structure and uses the nearest translation configuration.