Translation Management
The Content Manager translation management functionality includes features such as automatic generation of objects for translation, pre-translation of the content of the object, and automatic routing in a given workflow.
Translation Management is responsible for:
- Calculating inherited, requested and pushed languages
- Generating the required target languages
- Marking previous versions as out-of-date (deprecated)
- Triggering In-context Perfect Matching
If using SDL WorldServer for translation, refer to the SDL WorldServer information provided in this document.
If using SDL TMS for translation, refer to the SDL TMS information provided in this document.
If using File System for translation, refer to the File System information provided in this document.
- Identify the target languages for the object. These are the languages into which the object needs to be translated. The target languages for an object are:
- defined on the object itself in the metadata field requested languages.
- calculated based on the map in which the object is referenced.
The inherited languages are defined on the map in which the object is referenced. The number of levels from which these languages are inherited is configurable. This takes into account, maps that reference the object that are referenced by maps with other target languages.
- Check for a valid source-target combination for all required target languages.
Each target language must have a released source language from which the translation is prepared. The Generation Scheme in the translation configuration () defines from which source language the target language is generated.
- Generate the target language(s).
When the source language is released, all target languages are generated by Content Manager. By default, mandatory metadata is configured. Other metadata for the target language objects can be configured. You can create different configurations for each language and for each user group. For example, you can configure a different Chinese translation vendor for different user groups.
- Pre-translate the content for each language if a previous translation is available.
When creating the target language objects Content Manager pre-translates the actual content. The new released source language version is compared with the last previously released source language version. The comparison is done based on XML element level. The Comparison Elements definition in the translation configuration ( ) defines the elements that are compared and in what sequence.
- Download them one-by-one.
- Export a complete set of to-be-translated items, for example, from the inbox, or a report, or using the results of a search.
- Push them directly to a TMS system.
The result is a file or set of files where each file is marked as a target language as indicated in its filename (for example, German is indicated by de) and the xml:lang attribute.