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.
RE: Choosing the right word: Guidelines for our global audience
Subject:RE: Choosing the right word: Guidelines for our global audience From:"Wroblewski, Victoria" <victoria_wroblewski -at- usr -dot- com> To:"Kate Wilcox" <kwilcox -at- ensim -dot- com>, <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Mon, 1 Oct 2007 13:37:40 -0500
-----Original Message-----
From: Kate Wilcox
Sent: Monday, October 01, 2007 11:51 AM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Choosing the right word: Guidelines for our global audience
This goes beyond the typical spelling differences (color vs. colour) and
clear-cut differences in meanings [jumper (one that jumps) vs. jumper
(dress)]. I'm talking about common English words that have different
connotations to different readers and writers.
-----
Maybe the question needs to be, who is the end audience?
We do a lot of translations of our documentation, and each language may
have preferences for words/phrases that are not direct translations of
English, but how things are understood by that language's native
speakers. We write for understanding in US or UK English, and leave it
to the translators to figure out how to say it in other languages. Our
English docs are for a target US or UK audience or those who understand
US/UK English, while other target audiences get a localised language.
It seems like you have a situation of writers trying to impose *beyond*
straight English, they're trying to apply connotations from their native
language on to English. If your audience is English speakers in India,
let them have it and re-phrase as they, the speakers you're aiming at,
see fit. If your audience is English speakers beyond India, I'd stick
with the conventions of US/UK English, or you risk the waters getting
further muddied when a non-English speaker in another country is trying
to make sense of the documentation.
- V
This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately.
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-