 |
|
Localization can be a complex process, depending on the scale and complexity of the software in question. But an awareness of what localization entails can save a great deal of time and money. If developers design software with localization in mind, the entire process can be streamlined.
A Practical Guide to Localization, by Bert Esselink, is designed for all those involved in the localization chain, from software engineers and developers to translators, project managers and graphic artists. It gives a thorough presentation of the localization process, explaining the best way to design software to make localization easier, discussing the issues involved in translating and adapting software and documentation, and providing essential information for those who may be called upon to manage localization projects.
Localizing software is not as simple as it may seem at first glance. Not only does the program's interface and documentation have to be translated, but cultural differences need to be taken into account. (Is the target language written from left-to-right or from right-to-left?) Screen shots have to be updated, and, since different languages require different amounts of text to say the same thing, program interfaces may need to be redesigned.
Several chapters of this book cover documentation and online help, which can be affected by the choice of target language in unexpected ways. Such simple issues as the software used to write the documentation may even lead to difficulties.
For example, if documentation is created in a page layout program such as Quark Xpress or PageMaker, changes in the length of the text will change the layout, requiring additional DTP work to be done. Also, translators in many countries cannot afford such software. In addition, such software is very expensive, and the translator or localizer may need to purchase the program to translate the documentation.
Many languages have different writing systems than European languages -- Arabic and Hebrew, for example, are written from right to left, and not many word-processing and page-layout programs can handle these languages correctly.
The most useful lesson A Practical Guide to Localization provides is that successful localization is often the result of a careful examination of the process before the software is designed, so the software itself can be developed with localization in mind. Such simple strategies as not putting text strings in code, for example, can save a great deal of time and money, and these savings are multiplied by the number of language versions that will be made.
Since companies are increasingly focusing on a global market, localization is an indispensable part of software development. It is essential for all those involved to be aware of the key issues, both to save money and time and to provide the best quality software to their customers.
-- Kirk McElhearn (kirk@mcelhearn.com)
|
Explanation of ERCB rating scale:
|
