Translating the Ideas, Not the Words

[Susan Fowler <sfowler -at- EJV -dot- COM>]

Here are a few other suggestions:

Develop a dictionary of technical terms for the writers, programmers, and
 translators--if everybody uses the same words to describe the same thing, this
 reduces confusion. (The translator doesn't have to wonder if two words are
 supposed to be synonyms or if they mean two different things.) For example, if
 the person doing the interface puts "Process" on a button, the writers must
 talk about processes and processing, not "application" or "applying," for
 example, in the documentation, and define it as it is used for the translators.

Organizations that do controlled English have very specific rules for these
 dictionaries. For example, it helps to pick terms that are unambiguous--for
 example, the words "Switch" and "Default" have at least two meanings; if you
 use these types of words, you must say which meaning you have in mind.

Technical Communication and the Proceedings have articles about controlled
 English if you need more information (keep in mind that highly controlled
 English is not always good thing; semi-controlled English seems better).

Contact the American Translators Association or pick up their membership
 directory for translators who are familiar with the context as well as the
 language. (Walter Bacak is now the head of ATA, for those of you who used to
 talk to him at the STC office.) Call 703/412-1500 (Arlington VA).

Also, when looking for a translator, be as specific as possible re. the target
 country. For example, it seems that some computer terms vary in gender and
 other important characteristics from one South American country to the next.

--Susan Fowler
The GUI Style Guide co-author