The editor
Work through one target language at a time, with the source, your translation and everything known about the string on one screen.
The editor is where translations are written, read and approved. It shows one target language at a time: every key in the project, its source text, and the translation in that language. Open it from a project with Open editor, or from any Fill gap, Review or Approve link on the project overview, which open it already filtered to the strings that need you.
Choose a language
The strip at the top of the editor names the workspace, the project and the target language you are working in. Select the language to switch to another one; the list is searchable, and Manage locales at its foot takes you to the project's language settings.
If the project has no target language yet, the editor says Nothing to translate into yet. Someone with the Developer role or above has to add a target language first. If it has languages but no source strings, the editor says Nothing has been imported yet and offers Import source strings → (see Import content) or, for Developers and above, Add one key by hand.
Two ways to read a language
The toggle next to the language picks how the strings are laid out:
| View | What it is for |
|---|---|
| Side by side | The default. One string at a time: the source above, a large box for the translation below, and the glossary terms, memory matches and suggestions for that string beside it. The queue on the left lists every string in your current filter. |
| Table | Every key as a row, with the key name, the source text, the translation, a Quality column (on wider screens) and the string's state. Use it to scan, to select rows for bulk actions, and to open comments and plural forms. |
Queue at the top left shows how many strings are in view. On narrow screens it opens the queue as a drawer. Move through the queue with j and k.
Toolbar
| Control | What it does | Who sees it |
|---|---|---|
| Translate missing | Translates the strings in this language that have no translation, or whose AI draft is out of date, with Glossa. It reads Translating… while a run is going. See Translate with AI. | Developer and above |
| Run QA | Runs the automatic quality checks. It reads Checking quality… while it works. See Run a quality check. | Developer and above |
| New key | Adds a key by hand. See Add or edit a key. | Developer and above |
| ⌘ | Opens the list of keyboard shortcuts. You can also press ?. | Everyone |
| Filters, Views, Save view | Narrow the strings in view and keep that combination. See Filter the editor. | Everyone (saving a view needs edit access) |
Both Translate missing and Run QA show what the run covers before anything starts. See Translate with AI.
String states
Every translation carries one state, shown as a chip in the table, in the queue and in the context panel:
| State | Meaning |
|---|---|
| not translated | No translation exists in this language yet. |
| draft | Written by Glossa and not edited by a person since. |
| edited | Written or changed by a person, or imported from a file. |
| approved | A reviewer has approved it. |
| needs checking | Flagged for a person to check, by an automatic check or by a teammate. See Why was my translation flagged for review? |
A second chip, stale, appears when the source text changed after the translation was written. A string can be approved and stale at the same time. Translation states explains how strings move between states.
The context panel
The panel on the right, headed In context, shows everything known about the string you are on. Press [ to hide or show it. Depending on the string and your plan, it holds:
- Source: the source text, with placeholders highlighted, the translation's state, and its quality score and confidence when it has them.
- Overflow watch: the length of the translation against the key's maximum length, or a note that no limit is set.
- Glossary: glossary terms found in the source and how each must be translated, marked forbidden or do not translate where that applies.
- Translation memory: an exact match from earlier work, which you can take with Use this ($0).
- Similar approved translations: reviewed translations of similar source text, each with how close it is. Use this copies one into the translation. These are suggestions only.
- Ask Glossa: Suggest asks Glossa for a fresh draft of this one string and shows whether it passes the placeholder, plural, glossary and length checks. Nothing is saved until you select Accept. Available on Starter and above.
- Quality findings: each problem an automatic check found, with its category and severity.
- Approval: Approve and Flag, for reviewers. See Approve or flag a translation.
- Concordance: search earlier translations for a word or phrase, to see how your team has rendered it before.
- Provenance: the translation's recent versions, newest first, with Restore on each. See Version history.
In Side by side view, the glossary terms, the memory match and the suggestions sit next to the translation box instead, and the context panel drops them so nothing appears twice.
Translation runs
While a translation run is going, a progress card above the strings shows how far it has got, as Translating… (done/total), and rows fill in as strings land. Developers and above can Stop a run; strings already translated are kept. If a run finishes with failures, the card says how many strings failed, lists them under Show the strings that failed, and offers Retry failed, which re-runs only those strings.
What you can do depends on your role
| Role | In the editor |
|---|---|
| Translator | Read every string, write translations in the languages they have access to, comment, save views, ask for a check. |
| Reviewer | Everything a Translator can do, plus approve and flag. |
| Developer | Everything a Translator can do, plus start AI translation and quality checks, and add, edit and delete keys. Developers do not approve. |
| Admin and account Owner | Everything above. |
A member scoped to particular languages can read the whole project but only write in, and review, the languages they were given. See Roles and what each one can do.