Configure the terminology check

On the Settings Menu click QA Settings, or press F9. Select the option Terminology mistakes under the Terminology tab to activate this check.

General

Consistent use of dictionary

If you enable this option, QA Distiller will check whether source terms have been translated consistently throughout the translation, in case of multiple translation possibilities in the terminology list.

Tag-aware

If you enable this option, QA Distiller will only check terminology if terms are located between certain tags, specified as termLocation in TBX. Using this option, you can greatly reduce the number of false positives.

 

The XPath expression for termLocation in TBX is //tig/termNote[@type='termLocation']

 

Note: Tag-aware terminology checking does not work on translation units where the tags appear just outside the translation units.

ID-aware

If you enable this option, QA Distiller will only check terminology if terms are located between certain tags and if the ID of those tags matches. Using this option, you can achieve one-on-one terminology checking.

 

The X-Path expression for ID in TBX is //termEntry/@id

 

Example

 

Consider the following TTX file where the term Select appears three times in different locations.

 

 

Consider the following TBX file that has two possible translations for the term Select.

 

<termEntry id="QAD1">

<langSet xml:lang="EN-US">

<tig>

<term>Select</term>

<termNote type="termLocation">uicontrol</termNote>

</tig>

</langSet>

<langSet xml:lang="ES-ES">

<tig>

<term>Seleccionar</term>

<termNote type="termLocation">uicontrol</termNote>

</tig>

</langSet>

</termEntry>

<termEntry id="WIN1">

<langSet xml:lang="EN-US">

<tig>

<term>Select</term>

<termNote type="termLocation">uicontrol</termNote>

</tig>

</langSet>

<langSet xml:lang="ES-ES">

<tig>

<term>Añadir</term>

<termNote type="termLocation">uicontrol</termNote>

</tig>

</langSet>

</termEntry>

 

If you enable Tag-aware, QA Distiller will not check the term Select in the first sentence as it is not enclosed by the tag uicontrol.

 

If you enable both Tag-aware and ID-aware, QA Distiller will only match the terms with the corresponding ID.

 

Note: Tag-aware works on a whole string only basis, meaning that QA Distiller will only check terminology entries if the entire string between tags matches.

Source

Case sensitive

If you enable this option, QA Distiller will only check source terms that are case identical to the source term in the terminology list.

Space sensitive

If you enable this option, QA Distiller will only check source terms that have an equal number of spaces as compared to the source term in the terminology list.

Whole words only

If you enable this option, QA Distiller will only check source terms if the full word matches the dictionary entry (i.e. found independently, not within a larger text string).

Check for forbidden terms (TBX only)

If you enable this option, an error will be generated whenever a source term is found that has a forbidden status. The corresponding target term does not have to be present in the translation.

 

See also:

Forbidden terms in TBX

Target

Case sensitive

If you enable this option, QA Distiller will only match target terms that are case identical to the target term in the terminology list, and also generate an error message if the target term is not case identical to the target term from the terminology list.

Space sensitive

If you enable this option, QA Distiller will only match target terms that have an equal number of spaces as compared to the target term in the terminology list, and also generate an error message if the target term has a different number of spaces as compared to the target term from the terminology list.

Whole words only

If you enable this option, QA Distiller will only match target terms if the full word matches the dictionary entry (i.e. found independently, not within a larger text string), AND will generate an error message if the target term does not fully match the dictionary entry (i.e. found independently, not within a larger text string).

Check for forbidden terms (TBX only)

If you enable this option, an error will be generated whenever a target term is found that has a forbidden status. The corresponding source term does not have to be present in the source.

 

See also:

Forbidden terms in TBX

Forbidden terms in TBX

The TBX specification contains a data category that is useful for controlled authoring and controlled translation purposes. A term can be marked as approved or not recommended for use by setting the following picklist values for the termNote elements where the attribute equals administrativeStatus:

 

 

Select File > Setup and go to the TBX tab to specify which statuses are forbidden. The statuses notRecommended and obsolete are selected by default.

 

Example

 

<termEntry id="123">

<descrip type="subjectField">Software</descrip>

<descripGrp>

<descrip type="definition">To undo an action</descrip>

</descripGrp>

<langSet xml:lang="en-GB">

<tig>

<term>Abort</term>

<termNote type="administrativeStatus">notRecommended</termNote>

</tig>

</langSet>

</termEntry>

 

 

Note: Whenever a term is found with a forbidden status, QA Distiller will report it. Whether the source or target term is also present is not taken into account.