Introduction
This article is meant to explain how XTM processes files and common configuration requests. If you did not find the desired solution for the case you have in mind, please contact the XTM support team, and we will answer your questions as well as explain the reason of such behavior if the desired result does not happen to be possible to achieve.
What can be configured in terms of a source file?
In general, configuration is a set of rules that apply to the analysis of the project. Those rules can affect translation content (ITS rules), segmentation (SRX rules) and extraction of metadata from files.
Please, see particular elements of the source file which can be subject to configuration:
Definition of certain parts of the source file to, or not to, be translated;
Change of segmentation;
Segment IDs;
Segment comments;
Custom columns;
Multilingual Excel based on language codes;
Multilingual Excel based on predefined columns.
IMPORTANT!
Please, note that the segmentation/exclusion can be affected (and changed) by whether there is a certain formatting applied to the text:
link; bold; italic; underlined; strike-through; change of style used in text; subscript / superscript; color; background used for text …
… and other different modifications available for a specific file extension.
If you would like to change or in any manner modify the way your source files are processed, you would need to raise a proper ticket to the XTM Support team and provide all the details of your request which are listed in this article: How to request a new configuration or a change of an existing one. |
Configuration levels
In XTM there are four main levels of configuration:
Default configuration
It is the set of all rules for all configured file types that apply to the entire server and all the clients' accounts. If there is no configuration made on other levels, this is where XTM will always go to look for analysis rules.
Global level configuration
Those rules - if set - override the default configuration. They apply to all projects under all customers created for the selected client. Unless there is a separate configuration created for a specific customer or filter template, such global level configuration takes effect.
Customer level configuration
These configurations are made per customer on the client’s server. They apply to projects created under this selected customer. Unless there is a separate configuration created for a filter template, such customer level configuration takes effect. It also takes precedence over global level configuration.
Filter template level configuration
Filter templates (also called “analysis templates”) are used with projects and modify analysis rules only for selected projects. Each filter template has a unique ID assigned on the back-end side, which among others is used as template’s directory name. It is the strongest level and takes precedence over global level configuration as well as customer level configuration.
Please, keep in mind, that a given filter template can be restricted to be available under a given customer only.
IMPORTANT!
Filter templates can sometimes be confused with project templates, but those two are completely different. The filter template has rules for analysis of files, while the project template stores predefined settings for creating a project and allocating linguists.
You can create and set up simple filter templates in XTM UI on your own! Please, click here in order to see how to create as well as use filter templates in a project.
Good to know!
Every configuration requested can be set up on one of the above three levels. Setting configuration on a certain level means that it will override any corresponding configuration (e.g. for Excel files) with a smaller number next to it. |
|---|
EXAMPLE There is a configuration on a global level which excludes bold text from translation, but on a filter template level it is defined to translate bold text. Now, if we were to use the filter template during the project creation stage, or apply it in a project editor after its creation (and reanalyze the said project), this bold text would be extracted for translation. |