The editor

You edit one file at a time in the editor, in its source and in each target locale. Beside every block are the checks, the memory matches and the terms in force at the block's point.

A switcher in the header moves between the editor, the file-wide operations and the project's review session for the file. The web app and the desktop app have the same switcher.

Outdated wording

The narration uses terminology that has since been retired. The interface and the behaviour shown are unchanged.

Real-time collaboration

When teammates open the same project, you see their names and avatars on the blocks they are editing. Their edits and reviews appear in your editor without a refresh, and the progress bar moves as the team works. The server holds the saved content.

• One block at a time. Editing is per block, with no character-level co-editing. Every save names the version of the translation you opened.
• Conflicting saves. If a teammate saved a different translation of the block in the meantime, your save waits. The editor shows their translation beside yours and asks whether to save yours over it or keep theirs. Approving and rejecting work the same way, so a decision always applies to the wording you read.
• Checks on save. The project's checks run on every save. When they find a problem your wording introduces, such as a missing variable or a word the terms rule out, the editor lists the findings and asks whether to change the wording or save it anyway. A translation saved anyway is recorded with those findings.
• Offline. The desktop app keeps working offline. Edits queue locally and replay on reconnect.

See Real-time collaboration for the full picture.

Two views

The editor has two views, toggled from the header:

Visual

The default view places an inline editing card over a formatted document preview, so you edit each block in the context it appears in. The card shows the source with its natural formatting (bold is bold, links are underlined, placeholders render as chips), the target editor, optional reference locales, and per-block context: content memory matches and terms. Navigate block to block with the card's arrows or j/k; the preview scrolls to keep the active block in view. The preview can render source, target, or pseudo content.

Use the Visual view for careful, in-context editing, especially of blocks with inline tags, where the surrounding layout matters.

Table

The Table view lists every block in a two-column grid (source and target) with a status accent on the left edge. Click or double-click a target cell to edit it inline with the same editor the Visual view uses; press Enter to save and advance, Escape to cancel. A search box filters blocks by source or target text.

Use the Table view to scan a file and edit many blocks quickly.

Both views share the same data, inline editor and chip rendering. Switching views changes only how the file is laid out.

Inline tags

Many document formats contain inline markup (bold, links, placeholders, and so on) that the editor handles for you. In the default formatted view, text appears with its natural formatting applied. You can switch to the code view (click the </> button on the source) to see abstract tag chips.

When editing a target with inline tags:

• Flexible tags (bold, italic, links) can be freely removed, duplicated, or rearranged.
• Required tags (variables, placeholders, line breaks) must be kept in the target. The editor prevents accidental deletion and shows them with dashed borders.
• The tag palette above the editor shows source tags as clickable buttons.
• The validation bar warns in real time about missing required tags or duplicated non-cloneable tags.
• Use Ctrl+1 through Ctrl+9 to insert tags from the palette.
• Click the tag summary badge in the card header to expand the inline code legend, which lists every tag type with its constraints.

Tags look and behave the same in every file format. See Inline formatting for more details.

Per-block context

The Visual card shows the context for the selected block:

Checks

The findings the last run produced for the block, each with a severity, a type and a message, and the voice findings from the profile in force at the block's point.

Memory matches

Content memory matches for the block, each with a score (green for a 100% exact match, yellow for fuzzy), the match type, the stored source and target, and an Apply button that copies the match into the target, with the tags and variables the match holds.

Terms

Terms found in the block appear in the term sidebar with their source term, suggested target term(s), lifecycle status (preferred, approved, admitted, deprecated), and domain. Clicking a target term inserts it into the active target. With no target open for editing, the term is added at the end of the saved translation and its tags stay where they are.

Entities

Select text in the source and press ⌘E (Cmd+E / Ctrl+E) to mark it as an entity, for example a product name to leave untranslated. Marked entities are highlighted in the source and listed in the block context.

Progress tracking

The progress bar shows progress with colour-coded segments: gray (not started), yellow (draft), blue (translated), green (reviewed), plus a percentage, an X/Y translated counter, and a per-status breakdown. It updates in real time as you work.

Status bar

The bottom of the editor shows the current block position (Block N of M), source word and character counts, and target word counts.

Keyboard shortcuts

Key	Action
Enter	Start editing / save and advance
Escape	Cancel editing
Arrow Up/Down or j/k	Navigate between blocks
⌘E	Mark selected source text as an entity
Ctrl+1 through Ctrl+9	Insert tag from the palette

File-wide operations

The header switcher's Pre-process view runs operations over the whole file, before or instead of per-block editing.

• Pseudo-translate. Generate accented, length-expanded placeholder targets for the whole file. Pseudo-translation shows truncation, layout and encoding problems before any real translation is done.
• Recycle from memory. Pre-fill targets from the content memory across the whole file. Exact and high-confidence fuzzy matches land as drafts you can then check in the review session.
• AI draft. Draft every untranslated block with the workspace's provider or your own key, steered by the voice profile and the terms in force at each block's point. Start it from the editor's AI actions.

Each operation reports how many blocks it filled.

File export

Click Export in the header to download the file in its original format with all translations applied. In the browser this triggers a file download; in the desktop app the file is saved to disk and opened in your system file manager.