Software Internationalization Guide

The HP Internationalization Subsystem
Software Internationalization Guide—526225-002
4-18
Identifying Problems in the Application
internationalized application are interconnected. In internationalized applications the
environment variables might affect the locales, which in turn affect character
processing and the messaging system.
As Figure 4-1 on page 4-18 shows, the application inherits the internationalization
environment variables. After the application sets the locale it calls the
internationalization functions, which access the locale data.
These troubleshooting tips can help you locate the source of problems in an
internationalized application:
•
Did you follow the code preparation and testing guidelines discussed in Testing
Internationalized Applications on page 4-15?
•
Did you define the _IGNORE_LOCALE feature-test macro in your internationalized
application? Program modules compiled with the _IGNORE_LOCALE feature-test
macro defined use versions of the C library functions that do not support
internationalization and locales. _IGNORE_LOCALE causes the application to use
the C/POSIX default locale only.
•
If operating in the TNS environment, did you use the -l library operand and
specify the i18n library when compiling and binding your application with c89?
•
Is setlocale() using the correct locale name?
•
If starting the application from the shell? If you did, be sure that you exported the
locale after setting it.
•
Are the locale environment variables using valid variable precedence? Use the
locale utility to verify variable precedence.
•
Are the message source files correct?
Figure 4-1. Internationalization Subsystem Architecture
Internationalization
Environment
Variables
Internationalized
Application
Internationalization
Functions
French
. . .
Japanese
English
VST015.vsd