Home / Technical Translation
Technical and Engineering Translation
Technical documentation, translated by people who know the difference.
Manuals, specifications, safety documentation and technical files — translated with managed terminology, returned in your working formats, and laid out so they are usable rather than merely accurate.
What makes it hard
Technical translation is a terminology problem
Most technical translation is not difficult because the language is complex. Manuals are written plainly by design. It is difficult because for any given component, process or fault condition there are usually several defensible translations — and only one that the industry actually uses.
A translator without domain experience will produce text that reads perfectly well and uses the wrong word throughout. The engineer receiving it will understand what was meant and will not trust the document. On safety documentation, that gap between comprehensible and correct is where liability lives.
The second difficulty is scale. Technical documentation arrives as sets — a manual, a quick-start guide, labels, a training deck, an online help system — and the same warning must read identically in all of them. That is a terminology management problem before it is a translation one.
How we work
What careful technical translation involves
- 1
Terminology agreed before translation
A glossary is built or imported at the outset, so decisions are made once rather than repeatedly and inconsistently.
- 2
Domain-experienced linguists
Assigned by field — mechanical, electrical, software, process — because knowing the industry vocabulary is most of the work.
- 3
Prescribed wording respected
Safety phrasing, regulatory text and standard-mandated language are used as required rather than rewritten.
- 4
Structure and tags preserved
XML, DITA and structured authoring formats return with their markup intact, not flattened into prose.
- 5
Layout adjusted for expansion
German runs longer, Chinese runs shorter, and a layout built for English will not survive either without attention.
- 6
Second-linguist review
Every translation is read against the original before delivery — on safety documentation this is not negotiable.
What we translate
Technical documents we handle
Operating and maintenance manuals
For machinery, equipment and consumer products.
Installation and service guides
Including field service documentation and troubleshooting trees.
Safety documentation
Warnings, hazard notices, safety data sheets and compliance text.
Technical specifications
Datasheets, drawings, tolerances and material specifications.
Software and interface documentation
Help systems, release notes and API documentation.
Instructions for use, labelling and technical files.
Training and certification material
For operators, technicians and distributors.
Where technical precision meets legal drafting.
Timing
How long it takes
| Type of project | Typical delivery |
|---|---|
| Short technical documents Datasheets, single guides, specifications | 2–3 business days |
| Manuals and documentation sets Full manuals, structured content, multiple deliverables | Depends on volume and complexity |
| Multilingual documentation programmes Several languages, ongoing revisions, DTP included | Scoped before quoting |
Larger or more complex projects may require additional review time. Quotation requests are usually reviewed within 30–60 minutes during business hours, Monday to Friday, 8:00 AM to 6:00 PM Central Time.
Getting the best result
What helps a technical project go well
- Send your existing terminology. A glossary, a termbase or previously approved translations save time and produce a better result than anything we could invent.
- Send source files, not PDFs, where possible. An InDesign or XML source returns as a usable file; a PDF has to be rebuilt.
- Tell us the target markets. Regulatory and safety wording differs between them, and knowing early avoids rework.
- Flag which content is prescribed. If certain warnings must use specific wording, mark them so nobody improves them.
- Plan for updates. Documentation changes; translation memory makes later revisions inexpensive if the first project is set up properly.
Related services
Where to go next
Questions
Technical Translation, answered
Technical work is assigned to linguists with experience in the relevant field. This matters because technical translation is largely about knowing which of several plausible renderings is the one the industry actually uses. A bearing, a bushing and a bush are different components; a translator who has not worked in mechanical engineering will pick whichever sounds best.
Yes, and we would rather you send it than have us invent our own. If you have a glossary, a termbase, previously approved translations or even a product catalogue, send it at the outset. Where you have none, we build one during the first project and it stays with your account for everything after.
InDesign, FrameMaker, Word, XML, DITA, and structured formats from most authoring systems, alongside plain documents and spreadsheets. Tell us what you have and how the output needs to return. Where files carry tags or conditional text, we preserve the structure rather than flattening it.
Yes — desktop publishing is part of the work on most technical projects. Translated text expands or contracts, and a manual that runs a third longer in German will break a layout designed around English. We return files that are usable, not files that need rebuilding.
With particular care, because some of it is prescribed rather than free text. Warning wording, symbols and required phrasing are frequently defined by the standard or the market, and improving them is not an improvement. Where a market mandates specific language, we use it.
Short documents follow standard timelines of 2–3 business days. Manuals, technical files and multilingual documentation sets depend on volume, format complexity and how much DTP is involved. We scope before quoting so the date reflects the actual work.
Yes, and doing so together is more consistent than commissioning separately. A single source is prepared once, terminology is agreed once, and every language works from the same approved base — which matters when the same warning appears in twelve manuals.
Yes, and this is where translation memory earns its place. When a manual is revised, only the changed segments are retranslated. The rest stays identical to what is already published, and the cost reflects the change rather than the whole document.
Start your technical project
Send your files and any existing terminology, and a Project Coordinator will scope the work properly before quoting. Most requests are reviewed within 30–60 minutes during business hours.
Start Your Project →