TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Bad translations? From:Bernd Hutschenreuther <Bernd -dot- Hutschenreuther -at- PREPRESS -dot- DE> Date:Thu, 21 Jan 1999 13:16:56 +0200
As well for translations, as for new documents, it is important that the
person reviewing the documents does not only know the native language, but
also the native technical language and something about the contents.
I was glad that native English speakers proofed the texts I wrote in
English. We sat side by side, so I got hints immediately and could use them
in other documentations. Otherwise I could declare what I meant, when the
text was a little bit strange, or the proof reader did not know the
technical words.
Important for technical translations is not to translate too much.
Especially the translation of keywords, used in the program, causes much
pain afterwards, if the user, for example, types in "gehe zu" instead of
"goto" when describing a macro language.
(In some drivers there was used the translation "Bildschirm" for "Screen",
and the program did not work anymore in the German version.
