Glossaries
A glossary for every language pair.
DeepTranslate builds one glossary for each language pair from the files your newsroom already has: style guides, term lists, past subtitles. The engine applies it to every segment, so names, places, programme titles and house terms appear exactly as your editors write them, and their fixes keep it up to date.
Last updated 19 October 2026
How is a glossary built?
- 01
Send what you have
Style guides, past subtitles, term lists. Any format.
- 02
We build the pair glossary
One glossary per language pair, checked with your editors.
- 03
The engine applies it
Every segment uses your terms, every time.
- 04
Edits flow back
Corrections from your editors update the glossary.
What files do you need to build a glossary?
You do not need all of it. Most teams start with one or two of these.
| What to send | Typical formats | Why it helps |
|---|---|---|
| Existing term lists or glossaries | Typical formats: Excel, CSV, TBX | Why it helps: The fastest start: your terms go straight in. |
| Style guide or editorial guidelines | Typical formats: PDF, Word | Why it helps: Sets spelling, tone and how names are written. |
| Past subtitles in both languages | Typical formats: SRT, VTT, EBU STL | Why it helps: Shows how your editors actually translate on air. |
| Scripts or transcripts with translations | Typical formats: Word, TXT, your newsroom system export | Why it helps: Adds context the subtitles alone do not carry. |
| Names list | Typical formats: Any list | Why it helps: Presenters, places, institutions, programme titles. |
| Translation memories, if you have them | Typical formats: TMX | Why it helps: Reuses approved translations from past work. |
Not sure what you have? That is normal. We agree on the material together and help you find what is useful in your archive.
Why one glossary per language pair?
A term can stay fixed in French and need inflection in Luxembourgish. One shared list breaks one of them.
So each pair gets its own rules, and each grows with your edits.
Do DeepL and Google support glossaries for small languages?
| Feature | Generic engines | DeepTranslate |
|---|---|---|
| Glossaries for small languages | Generic engines: DeepL: 32 major languages only. Google: paid Advanced edition | DeepTranslate: Every pair we run |
| Learns from editor fixes | Generic engines: Manual re-upload | DeepTranslate: Ongoing |
| Built from your archive | Generic engines: No | DeepTranslate: Yes |
Frequently asked questions
What format do you need?
Whatever you have. Term lists, style guides, past subtitles and scripts all help, see the list above. We agree the details together and help you navigate your archive.
Who owns the glossary?
Your terms stay yours. Ownership and handover are agreed in the contract before the pilot starts.