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:Geoff Lane <geoff -at- gjctech -dot- co -dot- uk> To:TECHWR-L <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Mon, 1 Oct 2007 21:03:58 +0100
On Monday, October 1, 2007, Wroblewski, Victoria wrote;
> 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.
---
It's not just connotations - some words actually change meanings
between one country that calls its language "English" and another that
calls its similar, but subtly different, language "English". There are
enough differences between the two for American and English to be
distinct, but related, languages - and it's the same story if you
compare almost any two of the languages that call themselves
"English".
For example, in the automotive world many terms change meanings as
they cross the pond. As they move right to left, a "car" becomes an
"automobile", a "boot" becomes a "trunk", a "wing" becomes a "fender",
a "bonnet" becomes a "hood", a "hood" becomes whatever left-pondians
call the roof of a convertible car (or should that be "cabriolet").
Even the infrastructure isn't immune because a "road" becomes a
"pavement", and a "pavement" becomes a "sidewalk". Also, as a gallon
of petrol moves West across the pond it magically grows to become a
gallon and a fifth of gasoline.
Notwithstanding that, Kate's concerns over regional connotations are
valid. I worked for a Canadian company some years ago when my editor
returned my copy with a comment that one module invoking another had
connotations of demonic ritual. She suggested using "summons" instead,
and was shocked at my comment that in UK "to summon" has the same
connotations as "to invoke" seemed to have in Canada, and that a
"summons" was the same as a "subpoena". We ended up using "to call",
thus writing out both terms. Although it sometimes dilutes the
semantics for any one of the target languages, this is probably the
best option where you cannot localise for each.
For example:
US: Make sure you understand the requirements before you begin.
India: Make sure you appreciate the requirements before you begin.
Issue: The Indian writer considered "understand" to be rude. The US
writer considered "appreciate," and its connotation of recognizing
quality, to be too broad.
Rewrite to avoid both terms, e.g. "Ensure you have a good grasp of the
requirements before you begin."
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-
