HP-UX Reference (11i v2 04/09) - 1M System Administration Commands A-M (vol 3)

l
localedef(1M) localedef(1M)
LC_MONETARY Information in this category affects behavior of functions that handle mone-
tary values.
LC_NUMERIC Information in this category affects handling of the radix character in
formatted-input/output and string-conversion functions.
LC_TIME Information in this category affects behavior of time-conversion functions.
LC_MESSAGES This category contains information affecting interpretation of yes/no responses.
A locale definition file also consists of six categories. The beginning of each category is identified by a
category tag having the form
LC_category where category is one of the following:
CTYPE, COLLATE,
MONETARY, NUMERIC, TIME,orMESSAGES
. The end of each category is identified by a tag consisting of
the word
END followed by a space and the category identifier; for example,
END LC_COLLATE.
Categories can appear in any order in the locale definition file. At least one category specifications is
required. If a category is not specified,
setlocale() sets up the default ‘‘C’’ locale for that category
(see setlocale (3C) and lang(5)).
Each category is composed of one or more statements. Each statement begins with a keyword followed by
one or more expressions. An expression is a set of well-formed metacharacters, strings, and constants.
localedef also recognizes comments and separators.
More than one definition specified for each category constitutes a hard error (causes
localedef to exit
without generating a locale). Any category can be specified by the keyword
copy followed by the name
of a valid locale. This causes the information for the category to be identical to that in the named locale.
Note that the copy keyword, if used for a category, must be the first and only keyword following the
category tag.
A methods file is used to create locales for user-specific character encoding schemes.
Operating System Requirements
For cross platform development and development on a 64-bit operating system several requirements must
be observed. Both the 32-bit and 64-bit method libraries must exist. In the case of the 64-bit shared
library it must be in the directory ../hpux64 (orpa20_64 in case of PA-RISC systems) under the
location where the 32-bit library is located. When the -e option is specified, or when executing on a 64-bit
operating system, the resulting locale is placed in the directory hpux64 (pa20_64 in case of PA-RISC
systems) under the current working directory unless the install option has been specified.
Note
A locale built for one system cannot be used on other systems.
Users will not be able to generate PA-RISC locales on Itanium-based systems.
EXTERNAL INFLUENCES
Environment Variables
LANG determines the locale to use when neither LC_ALL or the other category variables specify a locale.
LC_ALL determines locale to be used. It overrides any values specified by LANG or any other LC_*
variables.
LC_COLLATE and LC_CTYPE have no effect on the processing of localedef, which behaves as if these
two variables were set to the C locale.
LC_MESSAGES determines the language in which messages are displayed.
International Code Set Support
Single- and multi-byte character code sets are supported.
RETURN VALUE
localedef returns the following values:
0 No errors occurred and the locale was successfully created.
1 Warnings occurred and the locale was successfully created.
2 The locale specification exceeded implementation limits or the coded character set used is not
supported.
>3 Warnings or errors occurred, and no output was generated.
Section 1M−−380 Hewlett-Packard Company − 2 − HP-UX 11i Version 2: September 2004