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: Using Contractions in Software Manuals From:Andres Heuberger <andresh -at- FXTRANS -dot- COM> Date:Tue, 11 May 1999 14:07:09 -0400
From a translation/localization perspective, use of contractions is not an
important consideration. Any good translator won't have any problems
understanding them. Conversely, it might be worth looking into the
qualifications of any translator who _does_ have problems understanding
contractions...
In translation, contractions are important, however, in that they often
point to stylist preferences on the part of writers. In our experience,
writers who use contractions often prefer a livelier, less monotone style
of writing.
That's good and fine but this does cause to make translation more
time-consuming and expensive because:
a) the more consistent and repetititve, the easier (read: cheaper/faster)
the translation
b) along with any increase in use of slang or jargon, the risk for
misunderstandings and mistranslations also increase
This is true for Eastern and Western languages alike.
Andres
------------------------------------
Andres Heuberger andresh -at- fxtrans -dot- com
ForeignExchange Translations, Inc.
Multilingual Compliance Management
888.454.0787 http://www.fxtrans.com
