What can be done

In short: a lot

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 XTM Support team and we will answer your questions as well as explain the reason of such behavior if the matter happens to not be possible to achieve.


What can be set up in terms of a hierarchy of a file (e.g.: XML) and/or regular expressions

  • Definition of certain parts of the source file to, or not to, be translated,
  • Change of segmentation.

What can be set up in terms of a hierarchy of a file:

  • segment IDs,
  • segment comments,
  • custom columns,
  • multilingual excel based on language codes,
  • multilingual excel based on predefined columns,

Please also note that the segmentation/exclusion can be affected (and changed) by whether a text is a link, bold, italic, underlined, strikethrough, change of style used in text, subscript/superscript, color, background used for text and different modifications available for a specific file extension. 



Levels of configuration


In XTM there are three main levels of configuration:

  1.  Global,
  2. Customer-specific,
  3. Filter template configuration.

Every configuration requested can set up on one of the 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.

An example:

There is a configuration on a global level which excludes bolded text from translation, but on a filter template level it is defined to translate bolded text. If we were to use the filter template during the project creation, or in project's details and reanalyze the project, the bolded text would be extracted for translation.