Document translation
One document, one target language, nine files back. The same nine in every order — no tiers, no packages.
Before a single word is translated, the system reads the document as a document: where the reading order runs, what is a table and what is body text, which terms recur and therefore have to stay consistent, which acronyms were defined and where, which numbers and formulas must not be touched, and which caption belongs to which figure.
Grouped by the question they answer, not by file type.
Nine files arrive in every order, unconditionally. The last two rows on the list join them when they apply to your document or when you select them — so you may receive more than nine, never fewer.
Nine files in every order.
Where is my document?
- document.docxThe translated document, in WordAlways included
An editable Word file — this is the anchor deliverable; every other file is derived from it or explains it.
Why this file exists
It is editable, not a picture of text. You can keep writing in it, comment on it, and hand it onward.
- document.pdfThe translated document, in PDFAlways included
Rendered from the Word file — for sending, printing and reading on any device.
Why this file exists
The PDF and the editable file stay identical, because one is produced from the other. There is no second version that went to somebody else.
- document.mdStructured textAlways included
The same content as clean text with headings and lists preserved — it drops into any editor, any notes app, any content system.
Why this file exists
When the content matters and the formatting does not, this is the file you don't have to fight. It is derived directly from the canonical document rather than rendered, so it cannot fail to render.
How do I know the translation is faithful?
- document_bilingual.htmlBilingual viewAlways included
Source and translation side by side, aligned paragraph to paragraph, opens in a browser.
Why this file exists
This is how you check a single sentence without reading two documents in parallel. It is in every order — not an add-on.
- terminology_sheet.docxTerminology sheetAlways included
Every key term in the document and the translation chosen for it.
Why this file exists
This is the file that answers the real fear: that the system quietly picked a term your supervisor does not use. You are not asked to trust the translation — you are handed the means to check it, and the same term in the same rendering from the first page to the last.
What was checked, and how was it decided?
- qa_report.docxqa_report.pdfQuality-control reportAlways included
What was checked in the document, what passed, and what was flagged for your attention.
Why this file exists
The full report, in every order. There is no short version and no paid "extended" report — there is one product, so there is one report.
- protocol.docxprotocol.pdfTranslation protocolAlways included
How the document was analysed and which translation policies were applied to it — document type, subject domain, and the decisions that followed from them.
Why this file exists
When you have to explain to a supervisor, a committee or a colleague how the translation was produced, this is the document that answers. It turns the process into something you can cite rather than describe from memory.
How do I read this comfortably?
- single_column.docxsingle_column.pdfSingle-column versionWhen applicable
The document flattened into one continuous column.
Produced when two or more columns were detected in the source.
Why this file exists
A two-column paper reads well in print and badly on a screen. This is exactly the same content, in a single reading order.
- side_by_side.docxside_by_side.pdfSource facing translation, in Word and PDFBy choice
The same comparison as the bilingual view, in a file you can print and pass on. Selected in the order form.
Why this file exists
The bilingual view is for checking on screen; this is for checking on paper, in a meeting, or with someone who reads only one of the two languages.
What happens to the structure
The system aims to preserve the source's structure, tables and reading order.
Tables stay tables, headings stay headings, and the reading order is reconstructed even where the source made it non-obvious. This is a measured aim, not a promise of an exact reproduction of the page layout.
What to translate
You don't always need the whole document. The scope you choose is what gets priced.
- The entire document
- Selected pages — a range or a list
- Abstract only
- A selected section
Scope is chosen in the order form, after the system has analysed the document and knows what is in it.
Ten localisation controls
Translating into a language is not only translating words. The defaults suit most documents; every one of them can be changed in the order form.
- Document type — auto-detected, confirm or change it
- Subject domain
- Target locale — which country the document is for
- Date format
- Unit system
- Currency handling
- Institution names
- Readability level for participant-facing documents
- Cultural adaptation — off by default
- Bibliography handling — keeping the source is recommended for citation accuracy
Approving terms before the final translation
You can ask for a pause after the glossary is built: the system shows you the key terms and the translation chosen for each, you approve or change them, and only then is the translation finalised. It is a checkbox in the order form.
What you can upload
- PDF — including scanned PDF
- Word — .docx and .doc
Every document comes back as Word, as PDF and as structured text.
- Up to 200 pages per document
- Up to 50MB per file
One order = one file, into one target language.
Once the paper is translated you can also understand it in depth and present it — an eight-part understanding kit and a deck, from the same document. Article kit