Creating a Multilingual Application

When developing a multilingual application, you have to balance a number of factors, including:

□ The time and cost spent developing, translating, and testing the translated application

□ The increased sales from having a translated version

□ Improved ease of use, and hence reduced support costs

□ The requirement for multilingual support

□ Should you create language-specific versions, or use add-on language packs?

You also have to decide how much of the application to translate, and which languages to support:

□ Translate nothing

□ Translate only the packaging and promotional documentation

□ Enable the code to work in a multilingual environment (month names and so on)

□ Translate the user interface (menus, dialogs, screens, and messages)

□ Translate the help files, examples, and tutorials

□ Customize the application for each location (for example, to use local data feeds)

□ Support left-to-right languages only

□ Support right-to-left languages (and hence redesign your UserForms)

□ Support Double-Byte-Character-Set languages (for example, Japanese)

The decision of how far to go will depend to a large extent on your users, your budget, and the availability of translators.

0 0

Post a comment