Brand voice
Tell Glossa how your product sounds, in every language or one at a time, and show it examples of what good looks like.
A project's voice is how its translations should sound: how formal, how warm, which words you always use and which you never do. You set it once in the project's Settings → Voice, and it travels with every translation request for the project.
Owners and Admins can change the voice. The style guide is available on every plan; inferring a guide from your work and the AI profile are included on Team and above.
The style guide
How you sound
The How you sound card holds the guide itself:
| Field | What it sets |
|---|---|
| Formality | How the product addresses the reader, from very informal to very formal. In French, for example, this is the choice between tu and vous. |
| Warmth | How much the writing sounds like a person, from clinical to very warm. |
| Brand voice | The product's personality in a line: the words you prefer and the ones you never use. |
| Regional notes | Anything true of one market and not the others, such as currency, address order, or a word that means something else there. |
| Anything else worth saying | Free-text guidance that does not fit the fields above. |
Lines you never cross
Lines you never cross holds two lists of rules: Always and Never. Type a rule and press Enter to add it. The card shows how many rules travel with each request and how long each can be.
One voice is not enough
One voice is not enough lets one language differ from the rest. Select Every locale to edit the base guide, or a language to edit its override. A language inherits the base guide and overrides only the fields you change, so German can be formal while Spanish is not, and both keep the same rules.
Save
Changes are not applied until you select Save changes in the bar at the bottom of the page. Discard throws them away.
Infer the guide from your work
Instead of writing the guide from scratch, select Re-infer from your work at the top of the page. Glossa reads the translations your team has already approved for the language you have selected (the first target language when Every locale is selected) and proposes a guide from them. The button reads Reading your work… while it works.
What comes back is a draft, filled into the language's fields: "Draft style guide inferred for de. Review it below, then save." Nothing is applied until you correct it and select Save changes.
Inferring uses your AI allowance and is included on Team and above.
The AI profile
On Team and above, the AI profile adds two things to the style guide.
Does it hold holds example pairs: a source string, the translation you want matched, and an optional note on why it is right. Glossa is told to match them. One pair you have already signed off often teaches more than any adjective. The card shows how many pairs travel with each request.
What it is built from shows what goes into every request, with three switches:
| Switch | What it decides |
|---|---|
| Use the glossary | Whether matched glossary terms are given to Glossa for this project. |
| Use the style guide | Whether the style guide on this page is applied. Turned off, the guide reaches no request. The applied to every draft pill at the top of the page switches the same thing. |
| Use semantic memory | Whether Glossa may draw on similar translations a person has already reviewed. See Translation memory. |
With an AI profile in place, quality checks also re-read what comes back and flag a translation that has drifted from the register you set. See Quality checks.
To go back to no profile, select Remove profile and confirm. Translations made from the next run on no longer use the profile; strings already translated keep their wording.
When changes apply
The voice applies to translations made after you save. It does not rewrite existing translations. To bring older strings in line, retranslate them, or run a quality check to find the ones that drifted.