The exact source string is preserved in every locale. Use for brand names, product SKUs, technical terms you've chosen to leave English.
Glossary
Brand consistency, enforced at the protocol level.
Your brand name shouldn't get translated. Your product family names should render the same way every time. The glossary makes that a property of the system, not a hope.
Which one applies to each term.
Force a specific translation per locale. 'trousers' → 'pantalones' in es-ES, 'pantalón' in es-MX. The model isn't asked to translate; the term is substituted.
Inject the preferred translation as a hint. The model may use it; quality scoring will validate.
Three glossary entries on a product page.
- · "BBYG" — DNT. Renders as "BBYG" in every locale.
- · "Premium Lottery Tickets" — Forced. es-ES: "Boletos de Lotería Premium". de-DE: "Premium-Lotterielose".
- · "Win big" — Suggested. es-ES preferred: "Gana en grande". Model can pick the local idiom if it disagrees; quality scoring decides.
How we make it impossible to drift.
Glossary terms are wrapped as model placeholders before the unit goes to the translation engine. Models see {{P1}} in the source string and {{P1}} in the output — no opportunity to translate or paraphrase them. After the model returns, we substitute the placeholders with the locale-correct rendering from the glossary.
Validators check that every placeholder round-trips exactly. If a model strips one (rare, but documented for older models), the translation is rejected and re-tried on the next tier up.
Industry-standard formats.
# Import TBX (TermBase eXchange)
paragraphs glossary import ./terms.tbx
# Import CSV (source, locale, target, mode)
paragraphs glossary import ./terms.csv --format=csv
# Export to JSON for source control
paragraphs glossary export --format=json > terms.jsonStart free in 30 seconds.
No credit card. 100,000 words on the free tier. Self-serve onboarding.