Language assets

Review terminology context and alternatives

Check extracted terms against their source context and an existing glossary before approving them.

Extraction produces candidates that need a translator’s judgment. Review context brings together source excerpts, existing glossary entries and related extraction candidates so you can decide whether to edit, approve or reject a term.

Review a candidate

Step by step with screenshots: Review the extracted terms.

  • Review context opens from a candidate in the extraction list, from Extract terms on a translated document or from an existing extraction in Glossary and terminology.
  • It shows up to three stored excerpts around the source term; excerpts may be shortened with an ellipsis.
  • The comparison uses one of your glossaries with the same language pair and separates identical bilingual pairs from alternative translations. Source context can be reviewed without a glossary.
  • Related candidates with the same source wording in the current termbase and language pair are listed (capitalization and outer spaces ignored), up to 20 existing entries and 20 candidates, with a notice when more exist.
  • Editing, approving and rejecting happen in the extraction list. A glossary selected inside Review context does not change the approval destination.

What approval does

Review findingResult when approving into that glossary
The same source and target already existThe existing bilingual pair is reused rather than adding another identical pair.
The source exists with a different targetThe earlier entry is preserved and the new target is retained as an alternative.
There is no matching source entryThe approved pair is added to the selected glossary.
An existing entry is marked forbiddenReview that usage label in the glossary. An identical-pair match is not a recommendation to use forbidden wording.

Choose the intended wording

After approval, open the glossary to set Preferred, Accepted alternative or Forbidden, and add a definition or usage example. Several targets can be correct in different contexts. Conflicting preferred targets are left unresolved by automatic glossary selection; review the alternatives for the selected segment.

Group expressions by meaning

Step by step with screenshots: Meaning groups.

  • A group holds up to 100 candidates from the same language pair and terminology base.
  • It has a concept name and a definition or usage note. You decide whether synonyms and inflected forms refer to the same concept in this context.
  • Group details can be edited, members added or removed, and a group removed while keeping every term. Concurrent changes are refused until the current group is reloaded.

Grouping organizes your review. It preserves each source, translation and approval state; it does not merge glossary entries, approve candidates or send a new instruction to the model. Review context also lets you open the meaning groups for that candidate.

Meaning suggestions use a local multilingual embedding model. They do not use your translation-word allowance or send your terminology to an external AI provider. Your administrator must install the local matching model before this option can produce suggestions.

Missing context and grouping limits

New extractions retain source excerpts. Older document-linked extractions may recover them from stored source segments. Older upload-only extractions may need to be extracted again. An empty context panel does not mean the term is incorrect.

Review context does not modify entries or call the translation model. The context panel finds literal variants. Suggest meaning groups compares up to 100 selected candidates with the locally installed language matching model; a proposed group is created only after you review its source and target expressions and their context. The local matcher is LaBSE. Its similarity score is not a confidence percentage or a translation-quality score: related expressions, negation and different numbers can receive high scores. Similarity is a hint, not proof that terms are interchangeable. Entries are never merged automatically. Manual grouping remains available when local matching is unavailable. Review the terminology before applying it to client work.