07
The memory library.
One memory per project is fine for a one-off. It stops being fine when a client keeps coming back, because ten jobs quietly leave ten memories that each know a tenth of the work. Library memories live outside any single project, filed under the client they belong to, so every job for that client draws on the same ones. As many per client as the work needs, ranked, each with its own mark-down for a memory you only half trust. Order decides where matches come from, Primary decides where your confirmed segments are written, and changing one never moves the other.
08
Client glossaries.
A glossary can sit in the project or in the library under its client, ranked exactly the way memories are, on purpose: one idea to learn rather than two. Fold the new termbase every job arrives with into the one you already have, and see precisely what would change before anything is touched. Nothing is ever removed by a merge, so a client sending a shorter list never deletes the terms they left out.
09
Character limits and subtitles.
Switch on the Chars column, set the maximum for the job, and every target shows its length against it and turns red when it goes over. Whole-segment, or per line, which is how subtitle limits actually work. Tags never count toward the number. Shift+Return adds a line break as its own chip, so you can reflow a target into as many lines as it needs whatever the source did. Subtitle files arrive as .srt converted by LinguaAI Terminology, in-cue line breaks intact.
10
Merge and split segments.
Badly segmented SDLXLIFF from an agency can be rejoined or broken apart without leaving the editor. Both operations follow Trados's own structural recipe, validated open, save, and reopen in Trados Studio, and the grid shows the merge gap in the segment-number column exactly the way Trados displays it.
11
Reading on iPad.
A pretranslation is far easier to judge when you read it the way it is meant to be read, as continuous prose, away from the desk. LinguaReview, the reading companion for iPhone, iPad and Mac, opens the same bilingual files, lays the translation out like a book, and lets you flag a sentence and leave a note. It never writes the file. Drop the sidecar into the project folder and LinguaTrans surfaces every flag as its own bucket, ready to work through.
12
The Admin link.
Optional, off by default. Switch it on and a project ties to the job it bills to: its value, status, and deadline on the project overview and the Home card, and client names drawn from your LinguaAI Admin list instead of free-typed. Mark a job In Progress or Delivered from LinguaTrans and it syncs back through Admin's own status logic, so the delivery date, activity log, and calendar all update as if you had done it there. The money statuses stay Admin's alone.
13
The LinguaAI suite.
File handoff between LinguaAI Terminology (convert .docx, .xlsx, .srt and .xml to XLIFF and back, plus unpack and repack Trados, memoQ and Wordfast packages), LinguaTrans (the bilingual editor), and LinguaAI Pro (AI pre-translate and review). Single-click handoffs in both directions, and the file always comes back whole. No shared databases and no hidden state between apps: the file is the contract. See the suite →
14
Mac-native throughout.
Swift and AppKit, built for macOS 26, with Liquid Glass on the chrome and the dense work surfaces left flat and legible, because glass behind text you stare at all day costs readability. A real Apple Help Book in the Help menu. Quick Look a bilingual file in Finder without opening the app. Native spell check, grammar, and Look Up in the target, with smart quotes, autocorrect, and predictive completion deliberately switched off: a translation is a precise rendering of a source, not a draft the system should improve.
LinguaTrans does not use AI, and your projects, memories and glossaries are plain files in folders you own. Nothing leaves your Mac unless you switch on the optional Admin link.