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:Re: Translations and addresses From:Steven Gaghan <sgaghan12 -at- gmail -dot- com> To:"Boudreaux, Madelyn (GE Healthcare, consultant)" <MadelynBoudreaux -at- ge -dot- com> Date:Wed, 6 Jan 2010 08:19:48 -0500
I have worked on Manuals that included addresses for a US-based office and
one in the Netherlands. These manuals were translated into multiple
languages, and so to were the addresses.
On Tue, Jan 5, 2010 at 5:38 PM, Boudreaux, Madelyn (GE Healthcare,
consultant) <MadelynBoudreaux -at- ge -dot- com> wrote:
> I have to include 2 addresses in our documents, one in the US and one in
> France, and I don't know whether to ask the translators to translate
> these country names or leave them in English. I don't know enough about
> how to mail works to know if having, say, Chinese characters on a letter
> might make it faster or slower to reach its destination.
> My gut reaction is that it should be in the local language, since the
> local postal worker is going to just read that part and put the letter
> into the box marked "USA" or "France" and the rest of the address will
> be dealt with in English or French, as expected.
> My liver, however, is telling me that if the letter somehow ends up in
> the "Europe" bundle and gets to, let's say, Germany, the German postal
> worker will now have no clue where the letter is going, and it may be
> held up. So using a lingua franca like English (!) may make it more
> likely to get where it needs to go.
> "Ask Google," said my spleen! "Google knows everything." Alas, Google
> was not forthcoming, although it did suggest to me that spleens are
> often wrong.
> My brain whispered, "Let's ask TechWhirl. They will know better than
> your digestive organs."
> Madelyn "Tuesday? Whazzat?" 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:
> 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:
> You are currently subscribed to TECHWR-L as sgaghan12 -at- gmail -dot- com -dot-
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit
> To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwr-l.com/ for more resources and info.
> Please move off-topic discussions to the Chat list, at:
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-