In the example below, the only difference between these pairs of segments is X20™ and X40™.
Once the X20™ segments have been translated, a regular TM finds no matches or only fuzzy matches for the X40™ segments:
But by adding X20™ and X40™ to the TM Variables, these items will be recognized as non-translatable elements, and will therefore be replaced automatically.
To achieve this, we go into Project Settings > Language Pairs > All Language Pairs > Translation Memory and Automated Translation, select our main TM, and click on Settings:
Then go to Language Resources and select Variable List from the list on the right-hand side, then click Edit:
Add both X20™ and X40™ to the list and click OK:
Close all the open dialog boxes and go back to the file, where we now get this:
Note: For this to work, each of the segments that had been previously confirmed in this example had to be confirmed again, so that the segment variables could be processed with the newly modified TM and the variables could be recognized and automatically replaced. From here on, any new segments entered into the TM that have either X20™ or X40™ will be automatically processed with the new variables.
Any number of variables can be added to a TM. This also works for things like product names and numbers with hyphens, such as 1375-2, 1379-5, for example, that Studio would not normally recognize as numbers.
Variables can be added or deleted from a TM at any time.
A new OpenExchange app for Studio 2014 called Variables Manager now makes it easy to add long lists of variables quickly to a TM through a simple copy-paste operation.