The grid, the shortcuts, the codes, the filters — all of it, and none of it reinvented.
This is the part that decides whether you could work in it on Monday. If you have been translating for fifteen years, you already know what you need on screen and what you need under your fingers. The question is only whether it is all here, and whether anything you rely on has been quietly left out.
You should not have to learn a new way to do the thing you already do well.
Two views, and the toggle is one button. Standard View is plain text: no tags, no chips, just the sentence you are translating. Formatting View shows bold and italic as bold and italic, and every other code as a labelled chip you can select, copy and move like a character. The same segment, the same file, whichever way you prefer to see it.
A segment opens with the text and none of the codes, and they go in afterwards — except formatting that wraps the whole segment, which is carried across for you. Before you leave the formatted view, the tool tells you how many segments carry formatting you placed. Edit one of those in the plain view, and its formatting is rebuilt from the source's when you come back, with a count of any that lost formatting, for you to review.
Translate without the codes and the vast majorityMeasured on a real 83-segment document: every code went back in with nothing to place by hand — 79 segments by rule, the last 4 by the AI model. go back in for you. Rules that read the source's structure place most of them; the few the rules cannot settle go to an AI model, which sees the segment with your project's stand-ins in place, exactly as every other request is.
Every placement is then checked by a separate tag checker. A segment it has any doubt about is marked for you to look at, with the reason on hover, rather than passed as done.
Filter on source, target or both, as plain text or a regular expression, then narrow by status and checks: unconfirmed, empty, missing a tag, or failing a term or rule. Each condition narrows the same view, and Ctrl+G can jump to the next match instead of hiding the rest.
Once set-up is complete, hold Ctrl+Shift+Space, speak, release. The transcript lands at the caret — replacing a selection if you made one — in Standard View or Formatting View, because the cell is editable in both. Who transcribes it is yours: a cloud Whisper, or a Whisper server on your own network, which costs nothing per minute and sends the audio nowhere. Until you set one up, the shortcut tells you where to do it.
Mandatory codes cannot go missing quietly: an export refuses while one is unplaced (a Trados or memoQ file warns instead), and F8 walks you to the next segment that still has one. Working without codes on screen is not the same as losing them. And the refusal is not "validation failed" — it names the code that is missing, the segment it belongs in, and, when there is a code to place, where to put it.
Right-click a source cell to fix a typo or a broken sentence: the original is kept in History, one click puts it back, and a translation already in the segment drops to draft so you look at it again. The correction is yours alone: an export writes your translation into the client's file, never your change to their source.
Confirm a segment and every repetition of it that nobody has worked on takes the same translation, in this file and in every file you have open with it; one already translated or confirmed is left as it is. Confirming also writes to your memory, and a segment you change afterwards is marked until it is sent again, so you can send just those in one go.
