Import and Export Glossary Files

Import terminology from structured or document files, review parsing, and export an approved reusable list.

Written By 4ALL.LIVE

Last updated About 1 month ago

Import terminology from structured or document files, review parsing, and export an approved reusable list.

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.

Step by step

  1. Prepare the source. Remove secrets, unnecessary personal data, duplicates, and low-value prose.
  2. Choose supported file. Use a supported structured file or approved document type; the UI parses document files through the glossary import flow.
  3. Select provider first. Sanitization differs for Azure, Google Chirp 3, and Speechmatics.
  4. Import and stage. Review filename, parsed count, and preview before applying.
  5. Read dropped-term summary. Correct invalid length/characters/duplicates rather than forcing them.
  6. Apply. Merge or replace only according to the intended workflow.
  7. Test terms. Use representative spoken sentences.
  8. Export approved list. Review the resulting file before sharing/reuse and label scope/provider/version.

What success looks like: The configured language service produces the intended accessible output with known quality, latency, usage, and recovery behavior.

Check your setup

  • The imported list contains only validated intended terms and its export can be reproduced without exposing unrelated data.

Troubleshooting

File unsupported

Convert to a supported structured/document format without macros.

Few terms parsed

Inspect file structure/encoding and extract a clean one-term-per-line or supported schema.

Too many terms

Azure real-time phrase lists should stay at or below 500; Google Chirp 3 adaptation supports up to 1,000 phrases, up to 100 characters each and 100,000 total adaptation characters per request.

Security and operational notes

  • Scan files according to policy.
  • Do not upload credentials or full confidential documents when only terms are needed.
  • Treat exports as sensitive configuration.