Language assets
Glossary
Store approved term pairs for a language pair and apply them during text translation, document translation, and review.
A glossary stores source terms and their translations for a language pair. A source term can have several alternatives. Relevant, unambiguous choices from your selected glossary can be supplied with a translation request; review the resulting wording in context. Available from the Starter plan up.
Create a glossary
Open Language assets → Glossaries
From the dashboard, open the glossary page. You can keep several glossaries: per client, per product, per language pair.
Add terms by hand or upload a file
Upload CSV or XLSX files, or add and edit term pairs directly in the interface.
Activate it where you translate
Toggle the glossary on in the dashboard translator or in the editors. The toggle shows how many terms are loaded.
Preferred, accepted and forbidden wording
Expand a glossary and choose Edit term to set a usage label, definition, example and notes. Preferred identifies the wording you want; Accepted alternative retains another valid translation; Forbidden marks wording to avoid. If different preferred targets conflict, automatic glossary selection leaves that source term unresolved. Forbidden entries are excluded from automatic model instructions. The selected segment resource panel flags forbidden wording found in the saved translation and missing preferred wording. These are literal matching checks, so review inflection and meaning yourself.
After a Word or editable PDF translation finishes, choose Terminology review in either editor. Pending edits are saved first. Enter the source term, current target wording and replacement, then preview. Only source segments containing that term are considered. Choose which eligible segments to change. Approved, confirmed and protected segments are excluded, and matches crossing formatting runs are left for manual editing. Applying saves drafts without consuming AI words. If the document changed since your preview, preview again. Project history can restore the old wording; Export rebuilds the download.
CSV import and export preserve status, definition and usage_example columns alongside source, target and notes. Importing the same bilingual pair updates it; a different target remains a separate alternative. Definitions and examples are reference information for reviewers.
How glossary enforcement works
The active term pairs are included with the translation request. After translation, a rule-based pass checks whether the required target terms are present and restores a missing or altered term where the rule applies. QA checks report remaining term mismatches per segment, with optional case sensitivity in CAT settings.
Use case sensitivity and morphology matching in CAT settings to control which source terms match. Review target wording in context and use glossary QA to identify missing terms. Separate Strict and Preferred modes are not offered.
For text that should never be translated at all (brand names, product codes, part numbers), use the non-translatables instead: supported URL, email and code protection, plus your own never-translate list under Language assets (Custom List). Add brand names explicitly. A glossary says "translate it this way"; a non-translatable says "don't touch it."
Review repeated glossary entries
In the glossary list, choose Review duplicates beside a glossary. Review each group with the same source and language pair. Keeping an entry removes only matching copies of its wording, status and explanatory metadata. Different translations, notes or definitions remain alternatives. If an entry changed after loading, reload the review before removing copies. Groups larger than 100 entries need review in smaller groups in the main library.
What belongs in a glossary
Use a glossary for terms where your organization has already chosen the target wording: product names, defined legal terms, interface labels, or recurring technical phrases. For example, both *pannello di controllo* and *cruscotto* can translate "dashboard" in Italian; the glossary records which one this project requires.
Don't have a glossary yet? Terminology extraction can build one from documents you have already translated.
Keep exploring
Terminology extraction and termbase
Find bilingual term candidates, review them, and link approved terms to reusable glossary entries.
Quality assurance checks
Check target segments for missing placeholders, formatting-tag differences, unusual length, inconsistent translations, and glossary violations.
Smart suggestions
Complete words and phrases from the active glossary, approved termbase entries, and Translation Memory while editing a target segment.
CAT settings reference
Translation defaults, translation memory, terminology, quality checks, protected text, and presets.