Feature
Every term, one translation.
Glossaries pin your terminology per language pair, with categories and notes, and enforce it on every job. Translation memory reuses the segments your reviewers already approved: exact matches come back locked, near matches arrive with a similarity score. Import and export TMX; XLIFF is supported.
The term base
One approved translation per term.
Not three, not five. One.
Ask three translators to translate your company name and you will get three answers. A glossary ends the debate once, then TranslateX enforces the answer on every job.
Glossaries
Your terminology, written down and enforced.
A TranslateX glossary is a term base per language pair: the source term, the one approved target term, a category, and a note explaining the choice. Legal, finance, governance, brand: Al Dana Holdings keeps 418 terms in its Arabic and English glossary, and every one of them is applied automatically whenever a document is translated.
Enforcement is the point. The glossary is not a reference document someone forgets to open; it overrides the model on every translation job in the workspace, from a one-page press release to a 200-page annual report.
- Term pairs per language pair, with categories and notes
- Enforced automatically on every translation job
- Visible in the review editor, per segment, as you work
Each term belongs to a language pair and carries a category and a note, so reviewers know why the term is what it is.
Translation memory
Sentences you already approved
should never be retranslated.
Institutional documents repeat themselves: the boilerplate, the disclaimers, the clause you spent an hour getting right. Translation memory keeps that work.
Exact and fuzzy matches
Exact matches lock. Near matches suggest.
Every segment a reviewer approves goes into the workspace translation memory. When the same sentence appears in a new document, TranslateX reuses the approved translation and locks the segment: no drift, no rework, no accidental rewording of legal language.
When a new sentence is close but not identical, the memory offers the stored translation as a suggestion with a similarity score. The reviewer sees exactly how close the match is and decides whether to take it, adapt it, or translate fresh. Machines reuse, humans decide.
- Exact matches reused automatically and locked in the editor
- Fuzzy matches suggested with a similarity score
- Only approved segments enter the memory, so quality compounds
Exact matches come back locked. Near matches arrive as suggestions with a similarity score, for a human to confirm.
Open standards
Bring your memory with you.
Take it with you too.
Teams coming from agencies or other CAT tools rarely start from zero. TranslateX speaks the standard formats, in both directions.
TMX and XLIFF
Standard formats, no lock-in.
Years of agency work usually live in a TMX file. Import it and TranslateX starts matching against your history from day one. Export works the same way: your memory leaves as TMX whenever you want it. XLIFF support keeps TranslateX compatible with established CAT workflows, so segments and their translations move cleanly between tools.
The result is a consistency system, not a silo: glossaries decide the words, memory decides the sentences, and both stay yours.
Your language assets stay portable. Nothing is locked inside TranslateX.
Beyond terms: style
Glossaries fix the words. The style guide fixes the voice, applying your organization's writing style to every file. Style governance →
Enforced in review
The review editor shows glossary hits and memory matches per segment, with statuses and QA checks, before the final document is rebuilt. Document translation →
Yours, wherever it runs
Glossaries and memories live with your deployment: cloud, sovereign cloud, or fully on your own servers. Security and on-prem →
Frequently asked questions
How do glossaries work in TranslateX?
A glossary holds source and target term pairs per language pair, each with a category and a note. Terms are enforced automatically on every translation job in the workspace, so the ministry name, the product name, and the legal phrase come out the same in every document.
What is the difference between an exact match and a fuzzy match?
An exact match means the new sentence is identical to one your reviewers already approved: the stored translation is reused and the segment is locked. A fuzzy match is close but not identical: the stored translation is suggested with a similarity score, and the reviewer decides.
Can we import an existing translation memory?
Yes. TranslateX imports and exports TMX, the standard translation-memory format, so years of past work from agencies or other tools start paying off immediately. XLIFF support keeps segment-level workflows compatible with established CAT tools.
How do new segments get into the memory?
Through review. When a reviewer approves a segment in the editor, it enters the workspace memory. Only approved segments are stored, which means the memory gets better with use instead of accumulating unreviewed machine output.
Who can edit the glossary?
Workspace roles control that: admins and managers manage language assets, while translators and reviewers work with them in the editor. See security and on-prem for the full role model.
Translate the document. Keep the design.
Right-click a file, work inside Office, or press F6 on anything on screen. TranslateX returns the same document in the other language: fonts, tables, and layout intact, terminology on brand.
Arabic, English & more · Layout preserved · On-premises available