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.
Globalization and Localization (was RE: Translate words or mea ning?)
Subject:Globalization and Localization (was RE: Translate words or mea ning?) From:Kent Newton <kentn -at- METRIX-INC -dot- COM> Date:Tue, 21 May 1996 08:14:00 PDT
On Tuesday, May 21, 1996 7:51 AM, Geoff Hart wrote regarding literal
translations vs. concept translations:
> ... let's consider a more complex (realistic?) example.
> What unpleasant connotations would (in
> the context of disk drives etc.) the concept of a "master/slave"
> relationship have for black Africans and Eastern European
> A simple and clear metaphor to most of us, but I suspect that it
> undesirable meanings for a non-North American audience.
I would contend that the "master/slave" metaphor is offensive to many
members of a North American audience as well. While I am far from
politically correct, I do try to use expressions that are not blatently
offensive, which the concept of master/slave most definitely is.
> This gets more complex still when the user interface itself isn't
> easily translatable among cultures. For example, if we're
> a user interface that uses file folders, file cabinets and a
> (e.g., the Mac OS) for users from a non-urban environment, would
> communicate effectively? I can see this as a problem if you're
> training native field staff to maintain products in the field in,
> a rainforest environment in which file folders are as common as
> Might we have to come up with a different metaphor that was easier
> Even between more compatible cultures, metaphors can go astray.
> read that the "typewriter keyboard" metaphor and interface that we
> for most computer interactions are problematic for many Orientals
> since the notion of a 100-key keyboard is entirely foreign to
> of cultures that use thousands of symbols for words. What problems
> this created for members of oriental cultures who must learn North
> American software?
With these last two points you're straying from the topic of translation
per se and moving into the realm of globalization and localization. For
any company planning to market its product (be it software, hardware, or
even services), the globalization of the product and accompanying
documentation is important and, of course, affects translation.
I would like to hear any success (or horror) stories in the area of
globalization and localization. As the world market shrinks, we are all
going to be selling our products (and accompanying documentation) in more
foreign markets. Globalization and localization is going to play a
larger part in the marketability of any product, and I think the
technical communicator can play a vital role in directing this.
Senior Technical Writer
kentn -at- metrix-inc -dot- com
Post Message: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Get Commands: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "help" in body.
Unsubscribe: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "signoff TECHWR-L"
Listowner: ejray -at- ionet -dot- net