Use the glossary
Set up your organization's glossary — create it, add items and per-language values, and verify the AI respects them.
Setting up the glossary takes ten minutes and improves every AI translation your organization runs from then on. Do it before the first big auto-translate batch — glossary fixes are never applied retroactively.
Create the glossary
Open LangSync → Glossary. The first visit prompts you to create the glossary: pick its default language — the language you'll write entries in, usually your product's source language. One glossary per organization, so this is a one-time step.
Add items
Click Add new item (or Add your first item in the empty state: "Add brand names, product terms, or other words that should be translated consistently across your content."). For each item:
- Value — the term in the default language (e.g.
Norcube). - Context — optional; add it when the term is ambiguous.
- Type — noun / verb / adjective / … / phrase / idiom. Helps the AI inflect the term correctly.
- Case sensitive — usually off.
- Translatable — off for anything that must stay verbatim (brand names, product names, identifiers); on for terms that have a fixed translation you'll provide.
Add per-language values (translatable items only)
Click an item to open its detail page, then Add translation: pick a language and enter the value. Each language you use here becomes an enabled language of the glossary.
You don't need values in every language. Where a value is missing, the AI translates that term normally — missing pairs mean "no constraint", never "translate as empty".
Verify on real text
Open Manual translation, leave Use glossary checked, and translate a sentence containing your terms. Toggle the checkbox off and re-translate to see the difference — the fastest way to confirm the entries do what you intended.
Where it applies from now on
Everywhere, automatically:
- Batch auto-translate — from the Translate missing dialog, term creation, bulk imports, and sync jobs.
- Single-cell suggestions in the side-by-side editor.
- Manual translation — via the Use glossary toggle (on by default). This toggle is the only per-call opt-out anywhere; batch flows always use the glossary.
Tips
- Start with non-translatable brand names. Easiest wins:
Norcube, your product names, anything trademarked. - Add fixed translations for high-value UI words. If your German
brand voice says
Übersichtwhere others sayDashboard, one glossary entry makes that consistent across every namespace forever. - Use context for ambiguous terms. "Backup (the Norcube product, not the verb)" saves the AI from guessing.
- Review the Complete translations column now and then — entries missing values in a language you actively ship are silent gaps in your terminology control.