The editor

The editor is where translation actually happens. You reach it by opening a target language from a project, and it stays on one language at a time — the one you are responsible for.

Layout

The screen has three parts:

• The file sidebar on the left, listing the project’s folders and files with the progress of each in the current language. Picking a file narrows the segment list to it.
• The segment list in the middle, one row per string.
• The editor panel on the right, for the segment you selected.

The header carries the language switcher, the progress bar for the language, and the counts per status.

Two views

Single language shows the source text and one translation column — the fastest way to work through a backlog. It is also where selection lives: tick several rows and delete them in one action.

Multi language shows every target language side by side for the same segment. Use it to check consistency across languages, or to spot which language is lagging on a particular key.

The choice is remembered per project.

Finding segments

The list filters by:

• Status — for example only needs_review when you are reviewing, or only untranslated when you are translating.
• Search — matches the key and the source text.
• File — from the sidebar.

Filters combine, and the list is paginated. A project with tens of thousands of strings stays responsive because filtering and paging happen on the server, not in the browser.

The segment panel

For the selected segment you get:

• Source text, with a button that copies it into the translation field — useful for strings that are mostly punctuation, numbers or markup.
• Context — the URL where the string appears and a screenshot, if a developer attached them. This is the difference between translating a word and translating a label.
• The translation field, which saves as a draft or submits for review.
• Plural forms — for a plural segment, one field per CLDR category the target language actually uses (zero, one, two, few, many, other), so a translator into Russian sees three fields where a translator into Japanese sees one.
• Markdown editing — a segment that came from a .md or .mdx file is edited as Markdown, block by block, with the document laid out the way it will be published.

Three actions on the segment itself sit next to the text:

Action	What it does
Edit source text	Rewrites the source and marks every translation outdated
Rename key	Changes the key your code uses; the translations follow
Not translatable	Marks a key that must ship as written — pre-translation skips it and export writes the source text

The assist panel

Under the translation field, four tabs answer the questions a translator has while typing:

• Translation memory — matches from previously approved work, each with a score from 0 to 100. One click drops the text in. See Translation memory.
• Glossary — the terms from the workspace glossary that occur in this source text, with their definition and the preferred translation. Forbidden terms are flagged here too. See Quality.
• QA — what is wrong with the translation you have typed: a variable dropped, an HTML tag unbalanced, a forbidden term used, one of your own regular expressions matched. Nothing here blocks you from saving or submitting — the panel reports, the reviewer decides.
• Comments — the discussion on this string, and whether it is resolved.

For an open project, a fifth tab lists suggestions left by non-members and lets a reviewer accept or decline them.

AI translate fills the field from a machine translation provider without leaving the segment — see AI translation.

Keyboard shortcuts

Shortcut	Action
Ctrl/Cmd + S	Save as draft
Ctrl/Cmd + Enter	Submit for review
Alt + ↓	Next segment
Alt + ↑	Previous segment
Ctrl/Cmd + Shift + W	Mark reviewed
Ctrl/Cmd + Shift + A	Approve
Ctrl/Cmd + Shift + R	Reject

The review shortcuts do nothing unless you hold translation:approve and the translation is in a status that allows the action.

Working alongside other people

The editor shows who else is in the project and which segment each of them has open, and a translation somebody else saves appears in your list without a reload. Two people editing the same string see each other before they collide.