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.
<snip> How do we
> determine the actually quality of the translations we are getting. We
do
> not have access to persons who first language is what we are
translating
> to. Thank you for any advice you guys can give me.
I can't imagine there's any adequate substitute for review by a native
speaker. If you're translating to a language, it must be because you
plan to sell (or are already selling) to speakers of that language. So,
as Sally suggested, you must have or be developing sales offices, or
channel partners, or some kind of presence. Maybe you already have a
customer or two who can be recruited to provide feedback on the
translations.
If none of those are possibilities, you might be able to locate native
speakers for at least some languages at a nearby college or university.
With any luck, you might even find someone in a discipline that makes
them familiar with some of your technical terminology.
A few days' work reviewing translations every now and then, at a nice
hourly rate, is something a college student or faculty member might jump
at. Just check references carefully and think about how you can validate
that they're doing good reviews -- maybe have them translate selected
paragraphs back to English.
HTH!
Richard G. Combs
Senior Technical Writer
Polycom, Inc.
richardDOTcombs AT polycomDOTcom
303-223-5111
------
rgcombs AT gmailDOTcom
303-777-0436
------
Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
produce desktop, Web, or print deliverables. Just write (or import)
and Doc-To-Help does the rest. Free trial: 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-