What to Test
- Does the product install correctly in a non-English
environment?
- Are there any warnings that occur while installing in a
non-English environment?
- Are messages generated from the installation localized?
- Can the product be removed correctly in a non-English
environment?
Where to Test
Test the installation of the product using all command line and
GUI installation interfaces.
How to Test
To test the installation of your internationalized product, first
run the product in a non-English
environment. For more information see Section 10.2,
Running Products in a Non-English Environment.
- Install the product. Look for any warnings or error messages
during installation, and be sure that all messages are localized.
- Run the product and look for any warnings or error messages
during this process.
- Test the removal of the product by removing the product and
then installing the product again, or by installing another
product to verify that the system packaging database has not been
corrupted.
Common Errors in I18n of Product Installation
The installation can fail in three common ways:
- An application is either not added correctly when installing
in a non-English environment.
- The adding of the application corrupts the packaging database
and does not allow other applications to be added or removed.
- The application cannot be removed correctly.
In the Solaris operating environment,
there are two ways to run your application in a non-English
environment:
- Run all applications in a non-English environment.
- Run one application in a non-English environment.
Running All Applications in a Non-English Environment
To run all applications in a non-English environment, select the
locale from the Options -> Language menu in the Common Desktop
Enironment (CDE). You can also restart CDE in the locale you wish to
run. For example, to start CDE in German, as root:
# LC_ALL=de /usr/dt/bin/dtlogin
Or you can copy the file /usr/dt/config/Xconfig to
/etc/dt/config/Xconfig and then modify the file
/etc/dt/config/Xconfig to change the
Dtlogin*language resource to German.
Running One Application in a non-English Environment
To run a single application in a non-English environment and other
applications in the C locale, first load the fonts for the locale
then set the LANG and LC_ALL environment
variables. For CDE applications, be sure that certain environment
variables are set correctly using the dtsearchpath
command. The paths to the fonts required for a locale are usually
listed in the file
/usr/openwin/lib/locale/<locale>/OWfontpath.
Use the xset(1) command to add the fonts. For some
European locales, no extra fonts are needed. For command line
applications, be sure to start another terminal emulator in the
target locale so that the output of the application is understood
correctly by the terminal emulator.
Note: the xterm(1) terminal emulator
is not internationalized and should not be used to test command line
applications.
For example, to run the dtmail application in the ja
locale:
system% cd /usr/openwin/lib/locale/ja
system% sed -e 's/$OPENWINHOME/\/usr\/openwin/g' OWfontpath | xargs -n 1 xset +fp
system% eval `/usr/dt/bin/dtsearchpath -csh`
system% setenv LC_ALL ja
system% setenv LANG ja
system% /usr/dt/bin/dtmail&
If you see the message:
Locale could not be set properly
This means that the ja locale is not installed on
your system.
When run in a non-C locale, the product should find all its
locale-specific files and information simply by knowing what locale
it is running in. The product gets this information from the
operating system's LANG and/or LC_ALL
values.
For Intel-based systems, locale-specific versions of Windows95 or
Windows NT are available for many locales. If the system has been
installed properly for a particular locale, the user is not
ordinarily required to set locale-specific variables. However, in
certain cases, a product may specifically require the user to set its
locale-specific variables.
top
Print-friendly Version
