What is technical translation?

The term technical translation generally refers to translations on engineering topics. It is also used at times for scientific content (journal articles, textbooks) and, more loosely, as a synonym for specialised translation (e.g., a will or a video game).

Here, I use technical translation to mean, roughly, translations of engineering texts for informational purposes—for instance: a car owner’s manual, a repair report on an overhead line catenary, a specification package for a canal, or a transistor catalogue.

A tighter definition by purpose: the aim of a technical translation is to convey information objectively so the reader can perform a specific task. Unlike scientific writing, technical writing is not about teaching theory or arguing for a hypothesis. One practical test is authorship: well-written technical text contains no sign of the author’s voice or subjectivity.

Because of this purpose, certain features prized elsewhere matter less here. Technical texts are not meant to be entertaining, decorative, or inspiring. That does not mean style is irrelevant. On the contrary, style is critical—but for one goal only: efficiency. The writing must be clear, concise, and unambiguous.

People sometimes say that literary writing shuns repetition while technical writing allows it. The first half is true. The second is not: technical translation doesn’t merely allow repetition; it requires it. Repeat terms—and even whole phrases—whenever needed to remove any doubt.

All of the above applies to technical writing as well. The following points are specific to translation:

• The translator must account for context differences between source and target (user environment, standards, sockets, units, etc.) and adjust so the text fits the reader’s action domain.

• Ask whether the context is clear enough for the reader to access what they need to do the job. If the document contains an illogical instruction, an error, or obsolete material, the translator may—and should—intervene and adapt.

Ultimately, the primary requirement is understanding the source. If you don’t know the field, how will you understand it?

Reference: The Technical Translator: The Sherlock Holmes of Translation? — Mathilde Fontanet

© 2025 Alejandro Moreno Ramos, www.ingenierotraductor.com