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:Bill Swallow <techcommdood -at- gmail -dot- com> To:Andrea Koenemann <a -dot- koenemann -at- gmail -dot- com> Date:Wed, 25 Mar 2009 21:45:05 -0400
> 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.
Option A provides the quickest possible turnaround.
> 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?
Upgrade to a better tool. SDL has the most widely used tools and most
robust technology out there for managing translation.
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-