Design globalized applications

Your goal in designing international application components is to create components that support national languages independently.

The support of one language should not interfere with the support of another language. The support of one language should not force any reduction in the function of the product for another language.

Your application should be able to support multiple languages simultaneously. For example, support for a double-byte coded character set (DBCS) language should not exclude support for single-byte coded character set (SBCS) languages. When you set up your libraries, consider using multiple textual data libraries, which can be dynamically allocated for testing, packaging, and delivery.

As you develop a globalized application for the iSeries™ server, you must consider these and other unique design issues that will affect the way you build and code your application.

• Checklist: Application design
  This table provides some guidelines that you can follow when creating an application with national language support.
• Globalization and localization
  The operating system controls the operation of programs and provides services such as controlling resources, scheduling jobs, controlling input and output, and managing data. It is designed to complement and extend the capabilities of iSeries servers to provide fully-integrated support for interactive and batch applications.
• Application arrangement and architecture
  When you design an international application, consider the ways that you can organize and structure your application so that it can be used in an international environment.
• User interfaces
  A user interface is the part of a software product that your customer actually sees.