...
The New template popup will open. There are two four configuration types for filter templates:
...
Define the configuration type → it can be a filter or , custom variables, Font mapping, or Segmentation:
...
Create your configuration → choose the file type for which you want to create a filter template. Select one of the following options from the dropdown:
MS Office Word;
MS Office Excel;
Multilingual MS Office Excel;
MS Office PowerPoint;
MS Office PowerPoint 97-2003.
...
If you do not want to reanalyze the entire project, you can always upload a new file to it via the Files tab. This file can be added to existing ones or replace one of them. In this case, only newly uploaded files are analyzed with the new configuration rules. if you upload a file with the same name and extension as one of the source files, the content of the existing file will be overwritten during analysis.
...
Additional options: segmentation & font mapping
Aside from standard options for specifying a configuration to identify translatable text in a document, the embedded XTM UI Filter Builder also offers some additional text-related possibilities to make use of.
Segmentation
You can configure segmentation rules in a new template at:
Project level.
Customer level.
| Note |
|---|
IMPORTANT! It is not possible to add a custom template at Global level. You can only add segmentation configurations in the existing global filter template. |
...
In the next and final section (Create your configuration), you first need to specify type of the file (File type), as well as source language (+Add language), for which you would like to configure the segmentation rules. Once you have selected a particular language, a list with corresponding segmentation rules (regular expressions) will be displayed.
The below screenshot demonstrates four segmentation rules, that handle four English honorifics with full stop:
(^|\p{Zs}|\p{Ps}|\p{Po}|(<[^>]*>))Mr\.→ Mr.(^|\p{Zs}|\p{Ps}|\p{Po}|(<[^>]*>))Mrs\.→ Mrs.(^|\p{Zs}|\p{Ps}|\p{Po}|(<[^>]*>))Ms\.→ Ms.(^|\p{Zs}|\p{Ps}|\p{Po}|(<[^>]*>))Dr\.→ Dr.
The expressions in question are set up to break a sentence into multiple segments in XTM Workbench (Break sentence → Yes) after the occurrence of a particular abbreviation in the text.
...
The segmentation in XTM Workbench, after applying such newly created configuration to a project, looks as follows. As you can see, sentences are broken into multiple segments after each and every occurrence of a particular abbreviation.
...
Font mapping
You can configure font mapping rules in a new template at:
Project level.
Customer level.
| Note |
|---|
IMPORTANT! It is not possible to add a custom template at Global level. You can only add font mapping configurations in the existing global filter template. |
...
Font mapping generally allows you to define which font needs to be used in the target file. You can condition the application of a particular font in the target file basing on the presence of another certain font in the corresponding source file, specific target language, or specific source font category. Font mapping in the XTM UI is based on configuration files for MS Word format.
The below screenshot demonstrates three font mapping configuration rules that are created within the framework of one filter template:
If a MS Word source file’s text is in Calibri → the target file will be in Times New Roman Bold.
If the target language of a MS Word source file’s text is Polish → the target file will be in Arial Black.
If the source language’s writing system belongs to the so called complex scripts (in which the shape or positioning of a grapheme depends on its relation to other graphemes, for instance, Arabic alphabet), and the target language is Japanese → the target file will be in Comic Sans MS.
...
| Note |
|---|
IMPORTANT! Note that you can add/set up a particular font manually by typing, and it will work but it will not add it to the list you see in the dropdown. Font list is hard-coded and is based on Windows default font list. |
...
Good to know!
The new or updated configuration is applied during analysis. If you change any configuration, full reanalysis of any project that was using this configuration is required to apply the changes to all the target languages/files.
...