Create and Edit a Glossary
Add event terminology that improves recognition/translation while staying within provider constraints.
Written By 4ALL.LIVE
Last updated 12 days ago
Add event terminology that improves recognition/translation while staying within provider constraints.
Best for: Multilingual producers, caption operators, accessibility leads, event administrators, and authorized language reviewers.
Before you start
Translation, target-language count, glossaries, and text-to-speech depend on event permissions, provider/model/language support, plan entitlements, usage allowances or wallet, and eligible BYOK configuration.
- Confirm source language and provider quality first.
- List approved target locales, terminology, voice requirements, and human review responsibilities.
- Test with representative content before distributing viewer links.
Steps

- Collect high-value terms. Names, brands, acronyms, products, places, technical phrases, and required spellings.
- Open Glossaries & Phrase list. Confirm event/provider/source mode.
- Choose glossary domain/scope. Know whether terms are event/provider-specific.
- Add terms manually. Use clean phrase text without duplicates or sensitive unnecessary content.
- Set weight when supported. Azure phrase-list weight is supported from 0.0 to 2.0; increase cautiously.
- Review validation. Read dropped-term and provider-limit feedback.
- Save and test. Speak terms in natural sentences and inspect source plus translations.
- Maintain. Correct, remove, and version terms as the agenda changes.
What success looks like: The configured language service produces the intended accessible output with known quality, latency, usage, and recovery behavior.
Check your setup
- High-value terms save successfully and improve representative captions without distorting unrelated words.
Troubleshooting
Glossary disabled
Auto source mode may not support it; select a specific source language.
Term dropped
Review length, character, count, duplicate, and provider sanitization feedback.
Accuracy worsens
Reduce weight/term volume and keep only distinctive high-value phrases.
Security and operational notes
- Glossaries can contain confidential names/terms.
- Do not treat adaptation as guaranteed replacement.
- Apply consent/privacy and retention rules.