Your glossary, held in every language.

Locked terms are bound into the prompt before a draft is written and checked again after it, in every locale, with the grammar around them intact. Forbidden terms are refused. Preferred ones win. And the list can be mined from what you already approved.

Start for free Read the entries

your term list

held in every locale

your term list

kinds of entry: 3
kinds of entry
import formats, TBX and CSV: 2
import formats, TBX and CSV
list, mined from approvals: 1
list, mined from approvals
and up, no term cap: Starter
and up, no term cap

Your terminology, enforced on every row the engine writes.

live: flip a term and its verdict follows. Locked terms are held, forbidden targets are refused, preferred renderings win

the glossary

source

drafts, with the glossary gate on them

de-DE

Transglot Memory verwendet wieder, was Sie bereits freigegeben haben.

Transglot · heldMemory · held

fr-FR

Transglot Memory réutilise ce que vous avez déjà approuvé.

Transglot · heldMemory · held

ja-JP

Transglot Memory は承認済みの翻訳を再利用します。

Transglot · heldMemory · held

ar-EG

يعيد Transglot Memory استخدام ما وافقت عليه بالفعل.

Transglot · heldMemory · held

mined from approved strings3 candidates, from 1,240 approved rows. Accept or discard

checkoutseen 41x

Glossaseen 27x

release notesseen 12x

A simulation, in your browser. The gate logic is real matching on the drafts you see; the drafts are a fixture, and a sentence you type is echoed per locale rather than translated. Nothing is sent anywhere.

in the product

The term list, with its flags.

Locked and forbidden terms, and preferred targets per locale. Enforcement is a project setting: off, warn or enforce.

do not translate

enforcement: off, warn or enforce

what a term holds

Three fields, and no ambiguity.

A term is a rule, so it carries the things a rule needs: what it applies to, what it forbids, and what it should become in each locale.

Do not translate: Product names, feature names and legal wording, held byte for byte in every locale, including scripts that would otherwise transliterate them.
Forbidden terms: The words you never want to see anywhere. A draft that reaches for one is refused rather than quietly corrected.
Preferred target, per locale: One approved word per language, so two translators six months apart make the same choice.

Start for free

org and project scope

enforcement

Bound before, checked after.

The glossary is one of four deterministic gates that run on every row of every run. It is not a prompt suggestion.

Do not translate

The term survives the trip, in every script, including the ones that would otherwise render it phonetically.

term "Transglot", do not translate

ja Transglot のご利用ありがとうございます

Forbidden target

A word you have ruled out is a refusal, not a warning nobody reads.

de forbidden: "Warenkorb ansehen"

de refused, held for review

Preferred target

One approved word per locale, applied consistently across the whole project rather than per translator.

en checkout

fr paiement, every occurrence

Case and inflection

Locked terms are matched with their surrounding grammar in mind, so an inflected language does not have to choose between correct and compliant.

ru Transglot

ru Transglot, declension around it

three kinds and two ways in

The glossary, read as a dictionary

locked · do not translate

A term that must survive every locale exactly as written: the product name, a feature name, a trademark. It is bound into the prompt and verified in the output, and the grammar around it is allowed to inflect.

ru: Transglot, with the declension around it, never Трансглот.

forbidden

A target the engine may never produce, in any locale. The old brand name, a competitor, a word legal struck. A draft that contains one is refused, repaired once, and refused again if it comes back.

never "Übersetzungsspeicher" for memory, in any locale; the product says Memory.

preferred

When a source word has two good renderings, the one you chose wins every time. One preferred word per term per locale, so a project never drifts between them across a thousand keys.

fr: "panier" for cart, never "chariot".

mined

Agents reads what you already approved and proposes the terms it finds you using consistently. You accept or discard each one, and the glossary grows from your own reviewed strings rather than from a kickoff spreadsheet.

proposed from 1,240 approved rows: 31 candidates, 27 accepted.

imported

TBX from a translation vendor, or CSV from anywhere. Terms come in with their locale targets and notes, and the four gates start enforcing them on the next run.

a vendor TBX and a spreadsheet CSV land in the same list.

obs. · the spreadsheet

A tab called Terminology that nobody opened after the kickoff, and a German button that used the old brand name for a year.

Retire it

checked deterministically, before any model is asked

QaRunner::preGate

getting one in place

You already have a glossary. It just is not written down.

Four ways in, none of which is typing three hundred rows on a Friday.

01
Import what exists
CSV and TBX come straight in, so a list that already lives in a spreadsheet or an old tool does not have to be retyped.
csv
tbx
02
Mine your own strings
Term mining reads the project and proposes the candidates that repeat, so the first draft of the glossary is your product rather than a template.
suggested
Team plan
03
Write it once, inherit it everywhere
Organization scope covers every project. Project scope overrides it where one product genuinely differs.
org
project
04
Let the gate teach you
Every refusal names the term it broke and the row it broke on, which is how a glossary gets accurate rather than long.
gate 3

where to read more

The rest of the quality story.

The other three gates

Placeholders, plurals and length run beside the glossary on every row. All four, every commit.

Translation memory

Approved wording is reused before anything is generated, which is the other half of staying consistent.

The lexicon

The whole product set read as a dictionary entry: senses, a conjugation table and specimen plates.

FAQs

What terminology owners ask first.

Is the glossary a prompt hint or a check?

Both, in that order. Locked terms are bound into the draft before it is written, and the glossary gate checks the result afterwards. A row that breaks a term gets one repair pass and is refused if that does not fix it.

Which plans include it?

Glossaries are a Starter and above feature. They are a boolean on the plan, not a counted allowance, so there is no cap on how many terms you keep. Term mining, which drafts a list from your own approved strings, is a Team feature.

Can a term differ per locale?

Yes for preferred targets: a term carries one approved word per locale. Locked and forbidden terms are flags on the term itself, so they hold in every locale rather than differing between them.

How do I get an existing list in?

CSV and TBX import from the Starter plan, or term mining over your own project from the Team plan, which proposes the repeated candidates and leaves the approving to you.

Does the glossary apply to connectors too?

Yes. Content pulled from a connector rides the same four gates as code strings, so the same terms are enforced whether the string came from a repository or a CMS.

works with what you already run