Typical user scenarios

You might encounter several multicultural scenarios on the system. This section lists common scenarios with suggested actions to be taken.

• User keeps default code set.

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

  The language-territory that is 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 you.

• User changes code set from the default code set.

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

  • When you have the existing data that requires conversion.

    Flat text files that require conversion to the preferred code set can be converted by using 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 required text fields within the structured files.

  • When you want to change to the other code set.

    Where more than one code set is supported for a language-territory combination, you can change to a nondefault locale by using the following options:

    • The SMIT Manage the Language Environment menu.
    • The chlang, chkbd, and chfont commands.