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: Contractions and Translation From:Gail Hodgson <gail -at- HPATO -dot- AUS -dot- HP -dot- COM> Date:Fri, 7 Apr 1995 13:34:27 EST
When writing for translation, don't forget your English-speaking readers.
If the rest of the document is in a conversational style, readers will be
comfortable reading contractions.
When you send any document to be translated, you should always provide a
translation glossary that contains definitions for jargon and any words
you may have used in a non-standard way. All you need to do is spell out
any contractions you've used, and the translators are as happy as can be.
I've read too many dreary documents that were written for translation ...
they don't contain any contractions, any words that can have more than
one meaning, any life! Be kind to your English-speaking readers. (Or should
that be English-reading readers?)
gail -at- hpato -dot- aus -dot- hp -dot- com