https://access.redhat.com/solutions/1351023
SOLUTION IN PROGRESS
This solution is in progress and will be completed soon for Red Hat customers.
- 已更新 2015年二月17日17:33 -
环境
- Red Hat Enterprise Linux 6
- glibc
问题
- What do LANG, LANGUAGE and LC_* environment variables mean?
决议
-
Some of LC_* variables are defined in an ISO document.
Following sentecnes are quoted from man page and the ISO document.-
LANG (see 'man bash')
Used to determine the locale category for any category not specifically selected with a variable starting with LC_.
-
LC_ALL (see 'man bash')
This variable overrides the value of LANG and any other LC_ variable specifying a locale category.
-
LC_COLLATE (see 'man bash' or 'man 7 locale')
This variable determines the collation order used when sorting the results of pathname expansion, and determines the behavior of range expressions, equivalence classes, and collating sequences within path- name expansion and pattern matching.
-
LC_CTYPE (see 'man bash' or 'man 7 locale')
This variable determines the interpretation of characters and the behavior of character classes within pathname expansion and pattern matching.
-
LC_MESSAGES (see 'man bash' or 'man 7 locale')
This variable determines the locale used to translate double-quoted strings preceded by a $.
-
LC_NAME
The LC_NAME category defines formats to be used in addressing a person, e.g. in a postal address or in a letter.
-
LC_NUMERIC (see 'man bash' or 'man 7 locale')
This variable determines the locale category used for number formatting.
-
LC_MONETARY (see 'man 7 locale' or 'man 5 locale'')
changes the information returned by localeconv(3) which describes the way numbers are usually printed, with details such as decimal point versus decimal comma. This information is internally used by the function strfmon(3).
-
LC_TIME (see 'man 7 locale' or 'man 5 locale')
changes the behavior of the strftime(3) function to display the current time in a locally acceptable form; for example, most of Europe uses a 24-hour clock versus the 12-hour clock used in the United States.
-
LANGUAGE (see 'info gettext')
While for the `LC_xxx' variables the value should consist of exactly one specification of a locale the `LANGUAGE' variable's value can consist of a colon separated list of locale names. The attentive reader will realize that this is the way we manage to implement one of our additional demands above: we want to be able to specify an ordered list of language.
-
LC_PAPER (see 'man paperconf')
When called without arguments, paperconf prints the name of the sys- tem- or user-specified paper, obtained by looking in order at the PAPERSIZE environment variable, at the con- tents of the file specified by the PAPERCONF environment variable, at the contents of the file /etc/papersize , consulting the values controlled by the LC_PAPER locale setting, or by using letter as a fall-back value if none of the other alternatives are successful.
-
LC_ADDRESS (see ISO document)
The LC_ADDRESS category defines formats to be used in specifying a location like a person’s home or office, for use in a postal address or in a letter, and other items related to geography, including natural language. All keywords are strings and may contain non- digits, and all keywords are optional. T
-
LC_TELEPHONE (see ISO document)
The LC_TELEPHONE category defines formats to be used with telephone services. All keywords are optional. The strings are not restricted in what characters they can contain.
-
LC_MEASUREMENT (see ISO document)
The LC_MEASUREMENT category specified which measurement system to use. It had the "copy" keyword and the keyword "measurement" with 3 possible values: 1 - the ISO 1000 system, 2 - the U.S.A. system, 3 - other. The "i18n" FDCC-set had the "measurement" set to 1, reflecting use of ISO 1000 measurements. T
-
LC_IDENTIFICATION (see ISO document)
The LC_IDENTIFICATION category defines properties of the FDCC-set, and which specification methods the FDCC-set is conforming to. Values must be supplied for all unless otherwise noted, and the operands are strings.
-