Translation

Domains

A domain steers terminology extraction toward the vocabulary of your field. It applies to termbase work, not to plain translation.

A domain tells the model which field a term belongs to. "Discovery" means something different in a legal filing than in a research paper; "positive" means something different in a lab result than in a marketing email. Setting the domain resolves those ambiguities when terms are extracted and aligned.

Domains apply to terminology extraction, not to plain translation. Choosing a domain no longer changes how a sentence is translated — to steer translation output, use tone for register and a glossary to pin specific terms.

The domains

General (the default), Legal, Medical, Financial, Technical, Manufacturing, Government, Marketing, Automotive, and Energy.

Pharmaceutical, Telecommunications and Insurance remain selectable and are handled as Medical, Technical and Legal respectively — the categories the model uses for that material.

How to use it

1

Choose a domain when you extract terminology

Choose a domain in the terminology extraction step to identify vocabulary from your field. It also applies to terminology alignment. The domain is not a translation-style setting; use tone for text translation, document translation, and segment retranslation.

2

Keep terminology settings separate from translation tone

The workspace may store a domain as document or translation-memory metadata. That label does not steer translation. Approved terms influence a translation when you apply them through a glossary or translation memory; tone controls its register.

What a domain changes

The domain is supplied with the terminology job, so an ambiguous term is read in the intended subject context and its translation is picked accordingly. A domain does not know your organization's preferred terms; record those decisions in a glossary, which does apply to translation.