Creating translation engines
When you create translation engines, you specify which linguistic resources are used during the preprocessing and translation stages of your project. Translation engines store all of your linguistic resources in one place so having translation engines makes the project creation process very easy. Creating translation engines saves you a lot of time, especially if you work with the same language pairs or with translation projects which share similar topics.
Before you begin
- Recognizable elements (for example, variables which must not be translated)
- Segmentation rules which are used for splitting the source content into segments, clarifying how to interpret words which function as one word (for example, specific words which function as one word when connected via a hyphen or a dash)
- Customized language resources (for example, a custom date-time format that you want recognized for a specific target language)
- In TMs, language processing rules have an impact on how segment matches are identified and retrieved.
- In translation engines, language processing rules impact reporting (for example, how words are counted) and other language processing.
- Segmentation of the source files
- Word counting
- Editing content in Trados Studio and Trados Online Editor
- Use the same language processing rule for all the TMs you included in a translation engine.
- Create translation engines which have the same language processing rule as the TMs included in the translation engine.
Failure to do this, can result in various conflicts around recognizing tokens and inconsistencies in expected results.
About this task
When you create a new complex resource which is based on other component resources, you can filter the component resources by two criteria: Current folder and above (default) and Current folder. Using the filtering criteria enables you to see and use exactly the resources you own or have inherited.
When you create translation engines, you bring together the following component resources: TMs (with their component field templates and language processing rule), termbases, language processing rules. When you select these component resources, use the available criteria for quick and accurate resource navigation.
You can configure translation engines with the same source and target language. When this TE is included in a project which has the same source and target language, the project is automatically marked as a restricted project.