 | |
These principles and practices of internationalization (I18N) testing provide general guidelines, methodologies and insight to help properly test your product to ensure it has been properly internationalized. The examples cited are drawn from a culmination of experience performing internationalization testing on products written in the C, C++, and Java languages for Solaris and Intel platforms. These web pages were written by Ken Frank, an I18N Software Quality Engineer in the Java Software Developer Environments and Tools group at Sun Microsystems, Inc. AudienceIf the internationalization process is not yet familiar to you, there are a number of books that can help. Please take a look at our Internationalization Bibliography. On the other hand, if you are familiar with the process in general, these pages present our shared experiences to further your knowledge of I18N testing. DefinitionsInternationalization is the process of designing and coding a product so it can perform properly when it is modified for use in different languages and locales. Localization (also known as L10N) refers to the process, on a properly internationalized base product, of translating messages and documentation as well as modifying other locale specific files. Assuming that there is not a separate base product for the locale, the localized files are installed at their proper location in the base product. This product is then released as a localized version of the product. Localizing a properly internationalized product in most cases should require no changes to the source code. Internationalization TestingThese pages contain the methodologies you will find useful for testing a product to ensure it has been properly and fully internationalized.
Internationalization ResourcesThese pages contain some information you will find useful when preparing a product for internationalization. Spring 1998 | ||||||||
| |
| ||||||||||||
Print-friendly Version
