Glossary and brand voice
How your terminology and your voice are applied to every translation.
A glossary fixes what words a translation uses. Brand voice sets how it sounds. Both are set per project, and Glossa reads both on every translation.
The glossary
Each project has a Glossary, available on Starter and above. A term is a word or phrase from your source text, with the wording each target language must use. A term can also be marked:
| Option | Meaning |
|---|---|
| Do not translate | Keep the term exactly as it is in the source, such as a product name. |
| Forbidden | A word that must never appear in the translation. |
| Case-sensitive | Match the term only with the same capitalisation. |
A term can also carry a Notes field for translators and the kind of word it is, such as a noun.
Glossary terms are matched against source text and enforced during translation and during quality checks; a translation that departs from a glossary term is flagged. In the editor, the context panel lists the glossary terms a string contains, and the Has glossary issue filter finds translations that break one.
How strictly a departure is treated is the Glossary enforcement setting on the project's Checks page: Off, Warn or Enforce.
You can add terms one at a time with Add term, import them from a CSV or TBX file with Import CSV or TBX, and Export them. On Team and above, Extract terms proposes candidate terms from your source strings; candidates are not enforced until you approve them. Developers, admins and account Owners can manage the glossary.
Brand voice
The project's Voice settings page describes how your product sounds in every language:
- How you sound: formality, warmth, a description of your brand voice, and regional notes.
- Lines you never cross: rules a translation must always or never follow.
- Per-language adjustments, so German can be formal while Spanish is not.
On Team and above you can also give Glossa example pairs of a source string and the translation you want, let it propose a voice from the translations your team has already approved (a draft you edit and save; nothing applies until you save), and choose whether the glossary, the style guide and semantic translation memory are used for the project.
Admins of the workspace and Owners of its account can change the Voice page.