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:British English From:Anthony Veeder <anthony -at- EMULTEK -dot- CO -dot- IL> Date:Sun, 10 Nov 1996 18:17:44 EET
Around the 21-23 August this year there was an active thread thread
on "Non-American English," where many of the points raised here
Here's my tuppence worth:
I am originally from Britain, living in Israel, and I work
in an environment that expects technical documentation to be
written in American English (at least the spelling). It took
me a while to get used to calling full stops "periods" (ugh!)
and brackets "parentheses."
The point is that the spelling ("o" in humour, etc.,) is the
least problem. Non-American readers just think "Oh, that must
be American" and continue without batting an eyelid. (Someone
should do an experiment to see just how many genuine spelling
mistakes American writers can get away with before the non-
American reader says "Is that *really* how Americans spell it?")
Although I have no statistics to prove this, I get the impression
that in most countries where English is taught as a second
language, British spelling is taught (unless the teacher is
American). Most people are taught "zed" for example, not "zee."
On the whole, non-Americans are more knowledgable about American
*spelling* and some slang (thanks to Hollywood) than Americans are
about British, Indian, South African, etc.
The real problem, of course is the cultural one. When I began
working in my current job, I reviewed all the existing documentation.
I came across one phrase - "ballpark figure" - that I simply
didn't understand, even from its context.
My fellow technical writer is American, and we often find that
phrases we use (in conversation) are so culturally and historically
tied to one country or the other, that one simply doesn't understand
what the other means.
Just this afternoon I warned her about being on a sticky wicket.
When she had to go, I threw out "well, chocks away!" (That last
one was intentional, I admit.) On the other hand she mentioned
a song she knows about "a bum in Trafalgar Square." Just ask any
Britisher what a "bum" is to understand my point.
1. Never mind about spelling. Non-Americans will be quite forgiving
over what they see as minor eccentricities.
2. Avoid *any* culturally- or historically-based phrase. That is
equally true for Brits writing for Yanks and vice versa.
3. Be careful that you don't use words that have unfortunate meanings
in the other dialect (as in the "bum" example above). Sometimes it's
hard to know, somebody mentioned a URL .
Remember that Australian, New Zealand and South African readers have
similar English to the Brits. In Canada, I assume, they have similar
English to that in the US. The Indian sub-continent might be a
completely different kettle of fish ("whole new ball-game"??). I get
the feeling that their written English is still very formal, and their
readers might expect it. But you can't write four different versions of
the same English manual, can you...? *can* you...? You can? Wow.
Anthony Veeder eMail: anthony -at- emultek -dot- co -dot- il
Technical Documentation Tel: +972-4-999-0044
Emultek Fax: +972-4-999-0050