Re: Document Translation Quality

Subject: Re: Document Translation Quality
From: Sally Derrick <sjd1201 -at- gmail -dot- com>
To: Richard Melanson <rmelanson -at- spirecorp -dot- com>
Date: Mon, 22 Feb 2010 08:38:23 -0600

"We do not have access to persons who first language is what we are
translating to."

Really? Who is selling your product in these other countries? Normally, I
would suggest sending a few pages of each release to the Sales team in that
country to get their feedback on the quality. Free review from employees.

If you truly have no one in those countries you can use, I would define very
strict quality testing requirements for each of the translation houses.
Something that requires test results to be returned to you, which you can
then review with the vendor. What text was reviewed, who translated it, who
reviewed it, what problem was found, what is the corrective action (could be
vague English text), and was the translation memory corrected? Make a big
deal about quality every time you talk to them so they stay aware and
conscious of it. The squeeky wheel gets the attention, right? :-)

The only other suggestion might be using your various translation houses to
check each other. I can see potential for issues with that, though. It
would have to be handled carefully.

Sally Derrick



On Mon, Feb 22, 2010 at 7:57 AM, Richard Melanson
<rmelanson -at- spirecorp -dot- com>wrote:

> May I please ask for advice or assistance. My group currently writes
> user manuals for solar equipment. Believe it or not, translating our
> documents has just come onto our plate. We have two or three translation
> house we use fairly regularly, but I have a question. 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.
> Rick
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> 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 sjd1201 -at- gmail -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit
> http://lists.techwr-l.com/mailman/options/techwr-l/sjd1201%40gmail.com
>
>
> 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:
> http://lists.techwr-l.com/mailman/listinfo/techwr-l-chat
>
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


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:
http://lists.techwr-l.com/mailman/listinfo/techwr-l-chat


References:
Naming a department: From: Paul Goble
Re: Naming a department: From: Gene Kim-Eng
Re: Naming a department: From: Janice Gelb
RE: Naming a department: From: Spectrum Writing
Re: Naming a department: From: Tony Chung
Re: Naming a department: From: Bill Swallow
Document Translation Quality: From: Richard Melanson

Previous by Author: RE: Unset? Can that be a verb?
Next by Author: Re: Collaborative authoring, production, and CMS?
Previous by Thread: Document Translation Quality
Next by Thread: RE: Document Translation Quality


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads