The difficulties of technical translations

Today a colleague wrote on a translators’ chat list:

“Technical manuals have always been a notorious field of terrible translation work, so it seems a little naive to think quality is of the utmost importance.”

My colleague could be right about that “notorious field of terrible translation work”, but I’m afraid he looks a bit too much at technical translations from the point of view of a literary translator.

Technical translations can be difficult for various reasons.

The following sentence is an example from a manual for a forklift I’m working on at the moment:

“This bug causes problems when scanning operator cards, resulting in misread card strings.”

“String” in this sense should be “tekenreeks” in Dutch. That would be the correct translation.

However, in IT they usually do not translate “string”, but leave it as it is.

Why? Because the IT people don’t know any better, that’s why. And that is because even the Dutch use English texts a lot.

That means that if I translate “card string” by “kaarttekenreeks”, they’ll reject the translation.

Moreover: the legacy translations have “string” a few times, always left untranslated.

The only thing I can do is keep “string” and consider it as “technical language”.

It’s not a matter of “terrible translation work”, it’s that as a translator you don’t have much choice.

I have an IT dictionary with translations for lots of IT words, but the clients never accept them. As a matter of fact, in my early days I lost a client when I applied it.

Plaats een reactie