XTM Cloud 13.8

Convert part of the source text into inline elements before translation and then restore the original text in the target file. This is especially useful for variables in text like %value% or $[value] and can be used to prevent accidental corruption of the variables by the translator. It also reduces the translatable word count. This processing can be set to work for all file types or as a part of a project-specific filter template.

Convert specific text in the source document to string metadata. For example, all instances where text is used to describe a context or string location can be automatically converted into a column in the XTM Workbench. There are no limits to the amount of metadata that can be displayed or the number of columns that can display it. The regular expression is only applied to the content that you have defined as metadata. This option needs to be configured per file type but can also be a part of the filter template.

Convert specific text in the source document to string length restrictions. For example, all instances where you have listed the string length can be automatically converted and used as the length restrictions in the XTM Workbench. This means warnings can be applied where the text is too long. The regular expression is only applied to the content specified by the regular expression. This option needs to be configured per file type but can also be a part of a filter template.

Convert comments added to source files into normal segment comments. This way additional context or string instruction can be carried over from source files.

Detect language codes in source documents. When defined, XTM Cloud will automatically place the correct target language in the correct area. For example, where text is used in columns and target languages need to be populated in adjacent columns, this is now automated reducing the post-processing work for multilingual files. In order to use a filter template like this, you have to use XTM language codes, and it needs to be configured per file type, but can also be a part of the filter template.

Detect String ID in the source document. When defined, XTM Cloud will automatically place the correct String ID under the segment. This enables you to use ID-based matching for Excel files. For example. when string ID-based matching is used in XTM Cloud it enables the user to use features such as linking images to segments or using the segment filter based on IDs in the XTM Workbench. It is very useful for software localization and dramatically improves translation memory matching. This needs to be configured per file type but can also be a part of the filter template.