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.
There are some things that can be fielded to people who don't work directly
with you, maybe -- maybe some production stuff, things like that. But in
this case, it is ESSENTIAL that the translators know you, be able to reach
you and communicate with you about questions and concerns.
I'm learning, as I prepare for a major translation effort here, that there
are a LOT of things that I have to do to be ready to pass off files to a
translator (we're going to use an external translation service), including
communicating about vocabulary, style decisions, etc.
I would absolutely not hand anything off to go into a black hole somewhere
and expect anything but a nightmare to come back out. I'd insist on a
meeting with the translators, and if you need to minimize the political
impact of that, I'd say that it's to make sure that you can help them with
issues with your file formats and to resolve issues of language use in the
English version.
Then I'd get together with the translator and plan an effective way of
handling the project.
I'd be VERY nervous about just handing off a file that way -- as you
obviously are. I'd be nervous about a "lead developer" insinuating
him/herself on a technical information issue.
And as a matter of fact, here's what I see as the crucial issue:
Ultimately, is he responsible for the success of the translation effort, or
are you? I'd make sure that's clearly determined, and that whoever is
responsible (and therefore accountable!) is 100% responsible for the
communication with the translators.
Good luck!
-Rebecca
-----Original Message-----
From: Mitchell Gibbs [mailto:gibbs -at- GNV -dot- FDT -dot- NET]
Sent: Friday, April 23, 1999 5:01 PM
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Subject: Foreign language translation of Winhelp rtfs
My company is preparing our main product for sales outside the U.S. To
date, no one has discussed the issue of document translation with me. (As
the sole technical writer, I'm plenty busy with the English version, so I
haven't brought it up.)
A lead developer has just asked me for my winhelp rtf source files, so that
he can send them to our International Sales coordinator. That person wants
to have "his translators" begin working on them. I don't know anything
about the translators' qualifications. I suspect we're planning German,
Spanish, Portuguese, and Italian versions of the software. I also suspect
I'll get these translations back and be expected to compile them.
I told the developer that it would help if the translators knew at least a
little about winhelp. Knowing that's unlikely, I advised that the
translators make sure they don't erase any hidden text, or change any
context strings, macros, and bitmap links.
I'd appreciate any other advice or warnings about translating winhelp rtf
files. (BTW, I "code" help straight up in Word, using my own macros, so I
won't be able to reap the benefits of any HAT's.)
Mitchell Gibbs
Technical Writer
Advantage Software, Inc.