Glossaries

Define product terminology with its meaning and locale scope, then share and maintain it across localization engines.

A product term can have an ordinary meaning that is wrong for your software. A glossary tells translation which concept the term identifies, how it should appear in a target language, and when a name should remain unchanged.

In the Studio 2.5 navigation, open Studio 2.5 → Knowledge → Glossaries. Otherwise, use the corresponding section in Infrastructure. Existing resource links still work.

Each glossary belongs to an organization and can be attached to several localization engines. Its name, description, and source-locale coverage organize the resource. The term text and hints supply the language guidance selected for translation.

Add a term the model can interpret #

  1. Create or choose a glossary in the intended organization and check its source-locale coverage.
  2. Select Add term and enter the source locale and source text. Choose Custom translation to set the exact wording for each target locale you add; one term holds all of them. Choose Keep as-is for a name that should stay unchanged in every locale.
  3. Explain the intended sense in the hint. For account, “a customer's financial account, not a sign-in identity” makes a distinction that the word alone leaves open.
  4. Attach the glossary to the localization engines that should use it. Inspect the saved terms and attachments.
  5. Translate an intended-use example and an unrelated-use example. Compare the output with the saved term and hint, checking whether the wording fits each use.

A hint is meaningful prompt material, not a hard condition that prevents every unrelated match. Glossary guidance is supplied to generation rather than applied as unconditional string substitution. Context retrieval explains how to compare source, output, and saved guidance when a term seems absent or is used incorrectly. The request view does not show which glossary terms an earlier attempt received.

Keep locale and script scope precise #

A keep-as-is term applies to every target locale. A custom translation applies only to requests whose locale matches one of its target locales; Locale resolution explains how locales match.

For a language written in more than one script, a custom translation applies only to requests whose locale implies the same script. Bare zh and zh-CN imply Simplified, while zh-TW and zh-HK imply Traditional, so save a Traditional term shared by both regions for zh-Hant. Locale resolution explains the script check and how language and regional coverage match.

Within one glossary, a source text and locale pair must be unique. Update the existing record instead of adding a competing duplicate. Across attached glossaries, candidates are ranked by locale and deduplicated; attachment order is not a reliable precedence mechanism. A small applicable pool can be preloaded, while a larger pool uses semantic retrieval. Check locale coverage, engine attachments, and the context you submitted before changing the term itself.

Bring terminology from another system #

Terminology transfer begins with the meaning of each field. Map source text, preferred target text, source and target locales, and hint. Preserve the distinction between a preferred translation and a name that should stay unchanged.

An assistant can inspect a sample from CSV, TSV, TMX, TBX, or a spreadsheet and propose that mapping. Review it before any write. Sentence-level translation-memory pairs are not automatically glossary terms: identify recurring concepts and use a rule only where examples support a reusable convention. Start with important terms and a bounded locale set.

To import, open the glossary and select Import CSV. The header names each column's locale: one source_text_<locale> column per source locale, such as source_text_en, one target_text_<locale> column per target locale, such as target_text_de, and an optional hint column. Fill one source column per row. A row without target text becomes a keep-as-is term.

Import adds new terms and overwrites terms the glossary keeps as-is, including their hint, so keep hints in the file. If a row matches a term the glossary already holds with translations, the import stops at that batch of 100 terms, and earlier batches stay saved. Edit that term in the glossary, remove its row and the rows already imported from the file, then import the file again. Through the API, updating a term's translations replaces the whole set, so include the existing translations you want to keep.

After each bounded batch, read back the saved records and compare fields and counts. For a failure or partial result, determine what was saved before retrying. Download CSV exports every term in the same layout.

Maintain shared terminology #

Inspect consumers before changing a glossary in use. A shared edit affects future requests from every localization engine that selects those terms. Detach the glossary when only one localization engine should stop using it; keep the common resource for the others. Resource grants explain who can work with it.

Remove all localization-engine attachments before deleting the glossary. Deleting a localization engine does not delete the organization-owned glossary. These operations have different scope, so choose the one that matches the intended change.

After a substantive edit, inspect a fresh matched translation. Successful storage establishes the saved instruction, not successful use of it. The term-definition guide develops the meaning and usage boundaries that make a glossary entry useful.