Language combinations
Also commonly referred to as language pairs.
A language combination consists of a single source language (i.e the language of the content to be translated) and a single target language (i.e the language the source content is being translated into).
Language Combinations are assigned to:
Linguists (In the user definition screen).
Customers (In the customer definition screen).
Tip
This is used to limit language combinations that can be configured in the terminologies and translation memory files assigned to this customer.
User Groups (in the user group definition screen).
Tip
The language set here overrides the language settings assigned to each individual linguist that is part of this group when the user group is assigned to a workflow step.
LSPs (in the LSP configuration screens).
Tip
There is only a need to configure language combinations when using multiple LSPs, each one with its own language expertise.
An individual project’s general section (in the project configuration screen).
Tip
This determines the languages that this project will be translated into and determines the linguists, user groups, and LSPs that are made available for allocation to the workflow steps.
A project templates details section.
Language combinations are configured in:
The configuration screens, by an Administrator using this procedure. This becomes a global configuration.
Note
By default, all language combinations are made available to everyone. There are hundreds of language combinations available in XTM.
The procedure indicated here merely limits the number of language combinations available to users globally in XTM, thus speeding up and simplifying their work.