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.
1. Ask Marketing about what addresses they want. They should be making this decision and supplying the content. This is one thing I would trust Marketing (or Sales) for.
2. You can either list ALL the various local addresses or use conditional text for all but the English one, then make visible only the addresses you need for a particular country.
Just my $0.02 (or the functional equivalent in various currencies).
Marguerite
--- On Wed, 1/6/10, Boudreaux, Madelyn (GE Healthcare, consultant) <MadelynBoudreaux -at- ge -dot- com> wrote:
From: Boudreaux, Madelyn (GE Healthcare, consultant) <MadelynBoudreaux -at- ge -dot- com>
Subject: RE: Translations and addresses
To: techwr-l -at- lists -dot- techwr-l -dot- com
Date: Wednesday, January 6, 2010, 11:48 AM
David Neeley held forth with a lot of useful stuff:
>Besides, what language is the documentation itself in? If English, then
>an English language address would seem a non-issue for the users.
It starts in English, but I'm asking about the translations, which are
in Brazilian Portuguese, Simplified Chinese, Traditional Chinese, Czech,
Danish, Dutch, Estonian, Finnish, French, German, Greek, Hungarian,
Italian, Japanese, Korean, Latvian, Lithuanian, Norwegian, Polish,
Romanian, Russian, Serbian, Slovakian, Spanish, Swedish, and Turkish.
Additionally, these are not localized. They go to many more countries
than the 28 languages suggest -- some countries get 2 or 3 languages;
some get just 1.
Leaving the addresses in English is certainly easiest on me, but not
necessarily the best for the user, for various types of users.... In
this case, I'm not particularly concerned about the person writing an
address on the envelope. That person is savvy and educated. The people
I'm concerned for are the superheroes, I mean postal workers, between
that person and us. If THEY have problems, it will hurt both the end
user and us, so I want to find the solution that makes sure they get the
info they need.
>However, given the rather infamous sensitivity of many French toward
the "corruption" of the language
>with English words, I would imagine that providing both forms of
addresses might be in order.
Oh, no. The French address is a different address, one in France, not
the English address translated to make the French happy!
***
Thanks for all the info and the thoughtful responses from everyone. I
love the suggestion of having the address in both languages, and I may
ask about doing that. This HAD occurred to me, but I fear for the
addresses being hard to read.
What do you all think about just offering the country name in both
English and the translated language? Would that cover a lot of
eventualities without being too complicated?
Sincerely,
Madelyn "More of a New Mutant" Boudreaux
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
---
You are currently subscribed to TECHWR-L as mkrupp128 -at- yahoo -dot- com -dot-
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
