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:Cultural stereotyping and internationalization From:"Bergen, Jane" <janeb -at- ANSWERSOFT -dot- COM> Date:Fri, 15 Aug 1997 10:27:36 -0500
While Susan's info gleaned from an STC workshop was very interesting, I
am meekly raising a flag here. We need to be careful of not making
cultural stereotypes. It seems to me that this workshop may have done
that by assuming Japanese are incapable/unwilling to tolerate
documentation written in active, direct forms, or that Arabs are all
sexist. I've lived in both Japan and the Middle East and have taught ESL
to students from both cultures. Believe me, stereotypes go phhhttt into
the wind when one has direct experience.
There is, of course, a possible *grain* of truth in these (Susan
Brown's/workshop) statements, but I think it would be appropriate to
proceed with caution in attempting to apply cultural issues when
internationalizing tech writing. Related cultural issues for audiences
include social class and education. You won't find the same "culture"
among educated, young, urbanites as you might find among village
farmers. And who uses the documents?
Just some thoughts to consider.
On Friday, August 15, 1997 7:08 AM, Susan Brown [SMTP:sbrown -at- jscsys -dot- com]
wrote:
> At the STC conference in Toronto in May there was a very
> interesting
> session, 'Lost in Translation'. The discussion primarily revolved
around
> being culturally sensitive in writing. I attended this session as we
have
> several online help systems that will be translated into French.
>
> Japanese was another language where voice is very important.
> Command type
> instructions (Insert the disk. Click the button.) are considered very
> rude:
> enough so that documentation written in this manner will NOT be used.
> Gender neutral language does not go over well in Arab countries. (If
you
> don't use the masculine, you must have something inferior.)
>
> Even simple things like how to list multiple authors can get
you
> into
> trouble. In North America, where authors are of equal importance, we
list
> the names alphabetically. In France, the women always get listed
first.
> In
> the Middle East and Asia, the men's names should come first.
>
> This doesn't only hold for translating: these issues must also
be
> taken
> into consideration when writing in English for a different culture.
> Colour
> use is also important: some cultures have strong negative associations
> with
> certain colours, and use of these in publications or software
distributed
> to these countries (i.e. red to Arab countries) can strongly influence
> document or product acceptance.
>
> As if we didn't already have enough on our minds.
I'm not attempting to ruffle feathers, rather saying take caution when
considering these issues.
Jane Bergen, Technical Writer,
AnswerSoft, Inc. Richardson, TX
janeb -at- answersoft -dot- com
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html