System Management Concepts: Operating System and Devices

Changing Your Locale

Changing the NLS Environment

You can change the NLS environment using the Web-based System Manager Users application or the SMIT Manage Language Environment menu to:

• Change the default language environment
• Change the keyboard map for the next system restart
• Manage fonts
• Convert the code set of message catalogs
• Convert the code set of flat text files.

You can also use the setmaps command to set the code set map of a terminal.

Changing the Default Language Environment

The setting of the LANG environment variable (the "LANG = <name>" string in the /etc/environment file) designates the default locale, which is a language-territory-code-set combination. The default locale provides formats for default collation, character classification, case conversion, numeric and monetary formatting, date-and-time formatting, and affirmative or negative responses. The default locale includes reference to the code set.

Changing the Default Keyboard Mapping for the Next System Restart

If more than one code set is supported for a given language-territory combination, multiple low-function terminal (LFT) keyboard mappings exist. The selected keyboard mapping must match the code set of the selected language environment.

Managing Fonts

Users can perform such tasks as selecting the active font and selecting the font to load for the next system restart. The selected font must support the same code set as the selected language environment and LFT keyboard mapping.

Converting the Code Set of Message Catalogs

Message catalogs are shipped in one code set for each translated language-territory combination. The code set of the message catalog must match the code set of the locale.

Converting the Code Set of Flat Text Files

User-defined flat files of one code set can be converted to another code set when appropriate (IBM-850 to ISO8859-1, for example).

Typical User Scenarios

There are several NLS-related scenarios some users might encounter on the system. This section lists common scenarios with suggested actions to be taken.

• User keeps default code set

  The user might be satisfied with the default code set for language-territory combinations even where more than one code set is supported. The user might keep the default code set if the current user environment uses that code set, or if the user is new and has no code set preference.

  The language-territory selected at system installation time is defaulted to the appropriate locale based on the default code set. The default keyboard mappings, default font, and message catalogs are all established around the default code set. This scenario requires no special action from the user.

• User changes code set from the default code set

  Users of a Latin-1 or Japanese locale might want to migrate their data and NLS environment to a different (nondefault) code set. This can be done in the following fashion:

  • When the user has existing data that requires conversion

    Flat text files that require conversion to the preferred code set can be converted through the Web-based System Manager Users application, the SMIT Manage the Language Environment menu, or the iconv utility. User-defined structured files require conversion through user-written conversion tools that use the iconv library functions to convert the desired text fields within the structured files.

  • When the user wants to change to the other code set

    Where more than one code set is supported for a language-territory combination, the user may change to a nondefault locale by using:

    • The Web-based System Manager Users application
    • The SMIT Manage Language Environment menu
    • The chlang, chkbd, and chfont commands.