TrueIdiom documentation
TrueIdiom is a human-in-the-loop translation platform: you submit text or a document, TrueIdiom translates it, checks the result against your quality bar, and sends anything below that bar to your own reviewers to approve. Approved work is published as a golden file you own and feeds your workspace’s translation memory, so repeat content comes back from memory instead of being translated again.
How it works
The same five beats run whether you work in the browser or over the API.
- Sign in. One guided sign-in creates your workspace — the container that holds your jobs, terminology, translation memory and golden files. See Getting started.
- Translate. Paste or type your source text, or upload a document, and pick your source and target language. Documents keep their layout; text jobs return inline.
- Automated refinement and quality check. The draft is re-read, assessed MQM-style — issues by severity and category, not one opaque number — and, where it falls short, repaired and verified again before anyone sees it. None of those passes are billed.
- Review. Work that clears your bar can publish on its own; anything below it lands in your Review queue for one of your own reviewers. They compare source, baseline and candidate, then publish as-is, edit first, save a draft, or reject.
- Publish and download. Publishing a text job — your reviewer’s approval, or the quality gate’s when the job clears your bar — makes it a golden record you can download as DOCX, PDF or plain text, and writes it into your translation memory. A document job’s translated file downloads in its original format as soon as the job is translated, and approving the document writes its segments into your translation memory.
Three ways to use it
The workspace. Everything works in the browser: submit a translation, watch the review queue, approve or edit, download the golden file, manage terminology and translation memory, and invite the rest of your team. Start at Getting started.
The REST API. JSON over HTTPS under a flat /api
prefix, authenticated with a tenant API key or an OAuth2 bearer token, and
versioned by date. Text translation runs inline and returns the finished job.
See the API reference.
Document translation. PDF, DOCX and XLSX are translated in place, with layout and formatting preserved, as an asynchronous job you poll. See Documents for the API, and Supported file formats for what goes down which path.
Key concepts
| Term | What it means |
|---|---|
| Golden translation | The published version of a translation — the one your team can rely on. Approving a job, or its clearing your quality bar on its own, publishes it as a golden record, downloadable as DOCX, PDF or plain text. |
| Translation memory | Your workspace’s store of published segments. Only published work goes in — approved by a reviewer, or cleared by your quality bar — never a draft; an exact match comes straight back from memory, verbatim, with no translation run behind it. You can also import an existing TMX file. |
| Terminology set | Your house terms for one language pair — or, for a CSV, every pair — uploaded as CSV or TMX, enforced during translation so the words you care about come out the way you spell them. |
| Quality gate and review queue | The check that decides whether a finished job can publish on its own or
has to wait for a person. Jobs that must wait sit in the review queue as
awaiting_review until one of your reviewers decides. |
| Workspace and roles | A workspace is one tenant: its jobs, terminology, memory and golden files, visible to no other workspace. Two roles exist — Administrator, who can invite people, change roles and see usage and billing, and Member, who can translate and review. See Roles. |
| Bring your own storage | Optional: route golden files and translated documents into your own Azure storage account instead of the platform store, with keyless access you can revoke. See Bring your own storage. |
Get started
Guides
Administration
Reference
Supported languages
Every language code the service accepts, how codes are matched, and which pairs are billed at the dense-script weight.
See the list →Supported file formats
What you can upload and what comes back: the layout-preserving document path, the text-extraction path, and the terminology and TM imports.
See the list →Limits & quotas
Upload and request ceilings, per-request character and batch limits, monthly allowances, and the rate limits — with the status each returns.
See the limits →Error codes
The three error body shapes, the stable detail tokens, every
error_code value, and what to do about each HTTP status.