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:Paresh Naik <paresh -dot- n -dot- naik -at- gmail -dot- com> To:Andrea Koenemann <a -dot- koenemann -at- gmail -dot- com> Date:Wed, 25 Mar 2009 13:12:31 +0530
In my group, we follow the method (A) since it gets the localized versions
faster to market. Also, the GUI terms get translated first and thus go in
the translation memory and terminology database first. This helps the
translators to use consistent terms when they are translating the
documentation.
For the clean up, I think you should look at how to better externalize the
GUI stings. We use Property Resource bundles that have key value pairs and
can be translated by using any CAT tool like Trados or Alchemy.
HTH.
Thanks,
Paresh
On 3/24/09, Andrea Koenemann <a -dot- koenemann -at- gmail -dot- com> wrote:
>
> 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?
>
> Thanks!
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> 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 paresh -dot- n -dot- naik -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/paresh.n.naik%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
>
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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-