Every translation-memory (TM) match has a Quality rating. This value is a percentage indicator of how well the text exactly matches a TM entry. An exact match will, therefore, have a Quality value of 100 (i.e. 100%).

However, if multiple 100% matches for a text segment are found in the TM, that segment will not be translated during pre-translation, and the correct translation must be chosen by the user.

NOTE: You can find a detailed description of the Translation Panel in the User Interface Description section of this Knowledge Base.

Alternatively, if no 100% matches are found in the Permanent/Approved translation memory (TM), then (by default) the segment will not be translated during pre-translation.

In this example, the 100% match is found in the temporary TM, as indicated by the yellow marker next to it. A 77.4% match has been found in the approved TM, as indicated by the green marker. Click the info button next to any translation match to see its source text.

NOTE: The Pre-translation Workflow Action can be set to also use the temporary TM. If that had been done here, the 100% match would have been applied to the segment automatically.

NOTE: Translation-memory results are case-sensitive. This means that (for example) a TM entry for Wind Power would be given a 90% quality rating if the text in the document was Wind power.

There are two types of translation memory (TM) available in one2edit™: Permanent/Approved and Temporary.

• Permanent/Approved: Any translation that is in the Language Set TM is a part of the Permanent/Approved one2edit TM. A Language Set TM is populated via the Commit Translations workflow action, and/or by importing a TMX (or XML) file. Selecting one2edit Translation Memory (Approved) from the Translate with drop-down menu shows only segments from the Language Set TM being used in this Job.
• Temporary: Any translation marked as Done in a Job becomes a part of the Temporary TM for the Language Set used in that Job. Therefore, any Job that uses the same Language Set will have access to these Temporary TM translations. Translations from the Temporary TM have not necessarily gone through any review/approval process, so must be treated with caution. This is why they are clearly marked with a yellow marker.

NOTE: A user may mark an untranslated segment as Done. This untranslated text will then be part of the Temporary TM. Therefore, it is good practice to use separate Language Sets for testing and production. This is also relevant when using the Commit Translations workflow action, as untranslated text that is pushed through a Workflow (e.g. during testing) will be committed to the linked Language Set TM. This is why care must be taken to ensure that the Commit Translations action only ever commits fully translated and reviewed segments to your production TM.