Synthesia pronunciation and Glossary: define a workspace terminology policy

SOURCE-BASED ANALYSIS · NO HANDS-ON RATING

Choose the right scope for each correction

Synthesia's pronunciation tool can adjust a term inside a video, while its Glossary applies workspace-level pronunciation and translation rules. Use a single-video rule for an exceptional script and a shared Glossary rule for a term that must remain consistent across projects. Confirm feature availability for the workspace before designing a process around it.

Separate three decisions

For each controlled term, record the written source form, the spoken form and the target-language form. A brand name can keep the same written form, need a special pronunciation and be marked not to translate. Keeping these fields separate makes review and CSV exchange less ambiguous.

Run a terminology fixture

Create a short synthetic script that includes every high-risk term in context. Preview the pronunciation, apply the rule to repeated instances where appropriate and generate a small sample. For Glossary rules, create a new translation or dubbed version because Synthesia documents that updated Glossary entries do not retroactively change an existing translated output.

1. Assign an owner and reviewer for each term.
2. Test the single-video pronunciation in the script editor.
3. Promote only repeated, approved decisions into the workspace Glossary.
4. Generate a new translation for every affected locale.
5. Archive the fixture results with the Glossary version date.

A controlled update example

A fictional software company changes the approved pronunciation of its module “AER”. The rule appears in twelve new training scripts and three older translated videos. Update the workspace rule, test a new fixture and list the older videos that require re-translation. Do not assume the previous outputs changed automatically. This is a planning example, not a measured product test.

Review import and workspace boundaries

Synthesia documents CSV exchange for Glossary terms and one Glossary per workspace. Validate language and locale fields before a bulk import, and keep separate approval records when the same terminology is used in multiple workspaces. A copied CSV is a transfer mechanism, not proof that the target workspace applied every term correctly.