Matches display template

From Omega-T 2.6, you can configure how entries are displayed in the Fuzzy Matches pane. DGT-OmegaT enables you to do the same  in the Search screens by using the «Configure format» option:

When you press the button "Configure format", the pane below turns to purple and displays a template:

The «Cancel» button restores the blank screen, while the «Reset» button simply restores the template to the last validated configuration. «Validate configuration» confirms your changes. However, they will not apply to the actual contents, only to the next search you will do.

Each screen type (directory, project, replace and pre-translate) has its own configuration: when you edit the contents of the purple screen, you are modifying the configuration valid for the current screen type. You may also note that the list of available variables can differ between the different types (for example, replace screen makes the distinction between original and modified target). If you want to modify other screens, you have to open a window for them individually, even if you do no search. But on the other hand, if you modify the template for one type, let's say the replacement one, it will apply to all replacement screens (but not pre-translate screens), including the already opened ones, but it will only apply for the searches you make after the change.

Note about existing variables

About the list of existing variables, you may note that some are preceded by @, instead of $. The difference is the following: $ is for pre-built variables, which correspond to something standard in Omega-T or in the TMX format ; @ is for properties, i.e. the following lines in TMX files:

<prop type="key">value</prop>

The TMX standard does not describe the list of available properties, so the list of @ variables is dependant on your business. OmegaT, for example, defines the key values such as id, prev, next… but this is only valid for project_save.tmx. Note also that these properties are only defined if the file is in tm/ directory, they are not filled for the project memory. In case you enter here a key which does not exist in the current entry, it will simply be replaced by a blank string.

This feature works for the Fuzzy Matches pane as well. This is also a feature in Omega-T since version 2.6, but I did not find any mention of @ variables in their documentation.