Why technical translation is a specialization of its own
Technical documents are read by engineers, designers, contractors and regulators. A wrong term or number doesn't just spoil the style. It leads to incorrect installation, rework and missed deadlines. That's why translating design documentation deserves the same care as developing it.
A translator needs to know more than the language. They need to understand the subject: how the process works, how working documentation differs from design documentation, how to read a drawing. Simon Akhrameev, who runs the agency, spent several years in the translation department of a gold exploration company, so mining and construction are our core subjects.
How we handle technical documentation
- Analysis and glossary. Before translating, we list the key terms and agree on them with you. If you already have a term base or previous translations, we use them.
- Translation in a CAT tool. The software stores approved translations, so identical passages are translated the same way in every volume.
- Quality control. Automated checks for terms, numbers, units and missed segments, followed by an editor's review.
- Same format as the original. Tables, numbering, title blocks and drawing labels stay where they belong.
English documents often use inches, feet and pounds, while documents for Russia and other CIS countries use the metric system and their own formatting rules. Depending on what you need, we keep the original values, add conversions in brackets or convert everything to metric. What matters is that the whole package is consistent.
Confidentiality
Design documentation often contains sensitive information about the site and equipment. All files are treated as confidential, and we're happy to sign a non-disclosure agreement before you send them.