The labeling of terminology in the segment is state-of-the-art in modern translation environments - as it is also the case in translate5.

Labeling of terminology

• A TBX file is turned over to translate5 during import.
• Based on the TBX, in all imported files the terminology gets labeled.
• On saving a segment the terminology gets labeled again.
• For terminology labeling, translate5 uses the openTMStermTagger by Prof. Klemens Waldhör, which is also licensed under Open Source. Aside from exact hits, XliffTermTagger also supports stemming and the use of upper and lower case letters. It is specified in translate5, which of these procedures is used.
• The terminology in the target segment is labeled, even if the corresponding source-language term does not exist in the source segment.

 For further configuration of this feature, see the openTMStermTagger plug-in.

Coloring of terminology

Target term not found: Red underlined

If a term is found in the source and the corresponding target term is not found in the target, the source term is underlined red. 

Target term found: Blue underlined

If everything is ok with the term, it is underlined blue.

Target term not defined in terminology: Brown underlined

Everything is ok, since a target term is not defined in the imported terminology.

Target term forbidden: Purple background

The term is marked as deprecated or forbidden in the terminology.

Please also see TBX file structure for information on how a term status in the TBX is mapped to a term classification in translate5.

Locking segments based on missing term translation

With the help of the translate5 plugins "LockSegmentsBasedOnConfig" and "NoMissingTargetTerminology" all segments can be locked, which do not contain terms which are underlined red.

This means, all segments are locked, where no terminology needs to be corrected. This can be used to correct terminology of Translation Memories in translate5.

Read more about the integrated terminology check: