A translation glossary should separate three decisions: the source term to detect, the exact text viewers should read, and the pronunciation the dubbing voice should speak. In TransCast, glossary terms inform transcription, subtitle wording, and speech pronunciation. Build the glossary before processing, then review it for every target language.
The three fields every dubbing glossary needs
| Field | Purpose | Example |
|---|---|---|
| Source term | Helps identify the word in source speech | API |
| Subtitle display | Exact text required in translated subtitles | API |
| Spoken pronunciation | Text supplied when the term is spoken | A P I |
Pronunciation is language-specific. A useful spelling for one target voice may sound wrong in another, so review the entry whenever the target language changes.
Which terms belong in the glossary
Add terms when the wrong translation or pronunciation would confuse the lesson:
- product, company, and person names;
- acronyms and initialisms;
- programming languages, libraries, commands, and file formats;
- words that must remain untranslated;
- established translations that differ from a literal translation.
Do not add every common word. A smaller, reviewed list is easier to maintain and less likely to force an awkward phrase.
How TransCast uses the glossary
Source terms are passed as transcription hotwords. When a source term appears in a segment, its display value guides the translated subtitle. Its pronunciation value is used for generated speech without changing what viewers read.
The output remains automated and still requires review. Confirm that the term occurred in the intended context and that the pronunciation sounds natural inside the complete sentence.
Build the glossary before processing
Scan the script, slides, interface, and existing documentation. Resolve competing spellings with the product owner, then ask the target-language reviewer to approve display text and pronunciation. For a course series, reuse the approved glossary across lessons; see online course translation.
For software walkthroughs, copy interface labels exactly and follow the product demo localization checklist. For conversations, include participant names and titles before dubbing a multi-speaker interview.
Technical tutorial review checklist
- Every required term appears exactly as approved in the SRT.
- Acronyms are spoken as intended rather than expanded accidentally.
- Commands, code, and URLs remain readable.
- The same concept has one translation throughout the video.
- A fluent reviewer has checked the term in context.