#Glossaries

Glossaries define preferred translations for important names, terms, and repeated phrases. They are one of the best ways to keep long projects consistent.

#What To Add

Add terms that should not drift:

• Character names, aliases, nicknames, and honorifics.
• Location names, institutions, factions, and organizations.
• Product names, technical terms, legal terms, and domain vocabulary.
• Repeated phrases that carry a specific tone or meaning.
• Words that are often mistranslated or translated too literally.

Do not add every common word. A glossary is most useful when it focuses on decisions that matter.

#Build Glossary Groups

Create glossary groups by project, series, client, genre, or subject area. This keeps unrelated terminology from leaking into the wrong translation.

Examples:

• One glossary for a novel series.
• One glossary for a client or brand.
• One glossary for technical manuals in the same domain.
• One glossary for subtitle conventions.

#Good Glossary Entries

A useful entry should be clear enough that another reviewer understands the decision.

Include:

• Source term.
• Preferred target term.
• Optional context or note.
• Optional disallowed alternatives when a wrong translation keeps appearing.

Example:

Source: Silver Court
Target: Corte de Prata
Note: Name of a political faction. Keep title case.

#Practical Workflow

1. Add obvious names and terms before the first translation.
2. Translate a short sample.
3. During review, add new recurring decisions.
4. Re-run only affected segments.
5. Keep the glossary small enough to maintain.

For strict one-off wording, use Chunk Overrides instead of adding a broad glossary rule.