Technical data

• Remove installed country support subsets (locales). If you do not have
superuser privilege, you can view, but not delete, installed subsets.
• Remove installed fonts. If you do not have superuser privilege, you can
view, but not delete, installed fonts.
• Establish a default login language, switch between dense code and
Unicode locales, and choose an input method for a locale that supports
multiple input methods.
• View installed keyboard map files. You do not have to be superuser to
view installed keymaps.
1.3 Setting Locale and Language
Locales are the method whereby the operating system implements
localization. A locale establishes information within a computer system that
is specific to each supported language, cultural data, and coded character set
(codeset) combination. A locale provides information on the following:
• Repertoire of available characters
• Language-specific sorting rules
• Language-specific rules and symbols for monetary and numeric data,
date, and time
• Path for translated message files, application resource files, help files, or
some combination of these
To view the locales installed on your system, use the command
locale -a
or use the Manage Locales option of the Configure International Software
utility.
See l10n_intro
(5) for information on the languages and codesets that the
operating system supports with locales. See locale
(4) for information on
the contents of a locale. This section describes the two types of locales (dense
code and Unicode) that Tru64 UNIX offers and how you establish a locale on
the operating system.
When Worldwide Language Support is installed on your system, two types of
locales are installed for localization support: Unicode locales and dense code
locales. Unicode locales conform to Unicode and ISO/IEC 10646 standards
and use UTF-32 as the wide-character encoding. Unicode locales whose
names end in UTF-8 use file and internal processing code defined in the
standards. Other, non-UTF-8 Unicode locales use traditional UNIX and
proprietary codesets for the file code and use UTF-32 for internal process
code. A subset of these locales have a @ucs4 modifier; they are provided for
backward compatibility and are the same as the locales without @ucs4.You
cannot select @ucs4 locales from the CDE login menu; you must specify the
locale name in the LANG environment variable.
Working in a Multilanguage Environment 1–3