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: When to translate what. From:"Maxwell Hoffmann" <mhoffmann -at- globalizationpartners -dot- com> To:"'Andrea Koenemann'" <a -dot- koenemann -at- gmail -dot- com> Date:Thu, 26 Mar 2009 20:41:57 -0700
Hello Andrea,
I work for a translation agency and method (a) is the most common one, used
by most of my current customers, and customers with previous positions. The
translation and LQA (Linguistic QA) process can be lengthy on "new"
translation, and make localized product release dates a challenge in
scenario (b).
Regarding your libraries, there are a number of translation agencies (my own
included) that can help internationalize existing code, or clean up a custom
database. Although the upfront costs may appear to be expensive, such work
will pay for itself in less than a year if you have typical release cycle
volume.
Your problems/challenges are common ones, and I'm glad that you asked the
question. Others on the list will realize that they are not alone.
_________________________
Maxwell Hoffmann
Director, Document Globalization Practice
Globalization Partners International (GPI)
www.globalizationpartners.com
tel: 866.272.5874 direct: 503.336-5952 mobile:
503.805.3719 fax: 202.478.0956
skype: maxwell.hoffmann email:
mhoffmann -at- globalizationpartners -dot- com
Follow me on TWITTER: http://twitter.com/maxwellhoffmann
Globalization Partners International, LLC provides document, software and
website translation services into over 100 languages including Arabic,
Chinese, French, German, Japanese, Korean, Portuguese, and Spanish.
Click here to see our latest service: http://tinyurl.com/gpi-doc-analyze
-----Original Message-----
From:
techwr-l-bounces+mhoffmann=globalizationpartners -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+mhoffmann=globalizationpartners -dot- com -at- lists -dot- techwr-l -dot-
com] On Behalf Of Andrea Koenemann
Sent: Tuesday, March 24, 2009 8:02 AM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: When to translate what.
Hi, we've been having some discussion here at work at how to refine our
localization process for GUI and documentation. How do you guys do it?
Option (A): First localize the GUI during development, at the same time the
documentation is being written in English. Second, send screenshots
(hopefully done) and the documentation for translation when the
documentation is done (always prior to release of our software in our
product life cycle... this can make accuracy hard but we try).
Option (B): Localize the GUI and documentation together after development is
done and the code is released.
Option (C): A different process entirely.
Plus: to throw a wrench into the works we use a development library that is
full of translations that are, apparently, incorrect (at least according to
our client). However, trying to differentiate which translations come from
the library, and are used in our software (we just get a complete language
file using QT Linguist with 4,000+ entries; plus another file for the stuff
our particular application has tacked on top), and need retranslation would
require someone go through the code, look at the software, find the
translation, and know the language. Any suggestions for how to clean up this
process?
ComponentOne Doc-To-Help 2009 is your all-in-one authoring and publishing
solution. Author in Doc-To-Help's XML-based editor, Microsoft Word or
HTML and publish to the Web, Help systems or printed manuals. http://www.doctohelp.com
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as
mhoffmann -at- globalizationpartners -dot- com -dot-
ComponentOne Doc-To-Help 2009 is your all-in-one authoring and publishing
solution. Author in Doc-To-Help's XML-based editor, Microsoft Word or
HTML and publish to the Web, Help systems or printed manuals. http://www.doctohelp.com
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
