When to translate what.

[Andrea Koenemann <a -dot- koenemann -at- gmail -dot- com>]

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 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