The purposes that locales serve are grouped into categories, so
that a user or a program can choose the locale for each category
independently. Here is a table of categories; each name is both an
environment variable that a user can set, and a macro name that you can
use as the first argument to
The contents of the environment variable (or the string in the second
setlocale) has to be a valid locale name.
See Locale Names.
This category applies to collation of strings (functions
strxfrm); see Collation Functions.
This category applies to formatting monetary values; see Generic Numeric Formatting Parameters.
This category applies to formatting numeric values that are not monetary; see Generic Numeric Formatting Parameters.
This category applies to formatting date and time values; see Formatting Calendar Time.
This category applies to selecting the language used in the user interface for message translation (see The Uniforum approach to Message Translation; see X/Open Message Catalog Handling) and contains regular expressions for affirmative and negative responses.
This is not a category; it is only a macro that you can use
setlocale to set a single locale for all purposes. Setting
this environment variable overwrites all selections by the other
LC_* variables or
If this environment variable is defined, its value specifies the locale to use for all purposes except as overridden by the variables above.
When developing the message translation functions it was felt that the
functionality provided by the variables above is not sufficient. For
example, it should be possible to specify more than one locale name.
Take a Swedish user who better speaks German than English, and a program
whose messages are output in English by default. It should be possible
to specify that the first choice of language is Swedish, the second
German, and if this also fails to use English. This is
possible with the variable
LANGUAGE. For further description of
this GNU extension see User influence on