-.\" Hey Emacs, this is -*- nroff -*-
-.\"
-.\" This file is part of locale(1) which displays the settings of the
-.\" current locale.
.\" Copyright (C) 1994 Jochen Hein (Hein@Student.TU-Clausthal.de)
.\" Copyright (C) 2008 Petr Baudis (pasky@suse.cz)
+.\" Copyright (C) 2014 Michael Kerrisk <mtk@manpages@gmail.com>
.\"
+.\" %%%LICENSE_START(GPLv2+_SW_3_PARA)
.\" This program is free software; you can redistribute it and/or modify
.\" it under the terms of the GNU General Public License as published by
.\" the Free Software Foundation; either version 2 of the License, or
.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
.\" GNU General Public License for more details.
.\"
-.\" You should have received a copy of the GNU General Public License
-.\" along with this program; if not, write to the Free Software
-.\" Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111, USA.
+.\" You should have received a copy of the GNU General Public
+.\" License along with this manual; if not, see
+.\" <http://www.gnu.org/licenses/>.
+.\" %%%LICENSE_END
.\"
.\" 2008-06-17 Petr Baudis <pasky@suse.cz>
.\" LC_TIME: Describe first_weekday and first_workday
.\"
-.TH LOCALE 5 2008-06-17 "Linux" "Linux User Manual"
+.TH LOCALE 5 2014-05-23 "Linux" "Linux User Manual"
.SH NAME
-locale \- Describes a locale definition file
+locale \- describes a locale definition file
.SH DESCRIPTION
The
.B locale
-definition files contains all the information that the
+definition file contains all the information that the
.BR localedef (1)
command needs to convert it into the binary locale database.
the only valid keyword in the definition is
.B copy
followed by the name of the locale which should be copied.
-.\" FIXME glibc 2.2.2 added new nonstandard locale categories:
-.\" LC_ADDRESS, LC_IDENTIFICATION, LC_MEASUREMENT, LC_NAME,
-.\" LC_PAPER, LC_TELEPHONE. These need to be documented.
+.SS Locale category sections
+The following category sections are defined by POSIX:
+.IP * 3
+.B LC_CTYPE
+.IP *
+.B LC_COLLATE
+.IP *
+.B LC_MESSAGES
+.IP *
+.B LC_MONETARY
+.IP *
+.B LC_NUMERIC
+.IP *
+.B LC_TIME
+.PP
+In addition, since version 2.2,
+the GNU C library supports the following nonstandard categories:
+.IP * 3
+.B LC_ADDRESS
+.IP *
+.B LC_IDENTIFICATION
+.IP *
+.B LC_MEASUREMENT
+.IP *
+.B LC_NAME
+.IP *
+.B LC_PAPER
+.IP *
+.B LC_TELEPHONE
+.SS LC_ADDRESS
+The definition starts with the string
+.B LC_ADDRESS
+in the first column.
+
+The following keywords are allowed:
+.\" Thanks to the kind folk who wrote localedata/locales/uk_UA
+.TP
+.I postal_fmt
+followed by a string containing field descriptors that define
+the format used for postal addresses in the locale.
+The following field descriptors are recognized:
+.\" From localedata/locales/uk_UA:
+.RS
+.\" .TP
+.\" %n
+.\" BUG: %l escape sequence from ISO/IEC 14652:2002 is not supported
+.\" by glibc
+.\" Person's name, possibly constructed with the
+.\" .B LC_NAME
+.\" .I name_fmt
+.\" keyword.
+.TP
+%a
+Care of person, or organization.
+.TP
+%f
+Firm name.
+.TP
+%d
+Department name.
+.TP
+%b
+Building name.
+.TP
+%s
+Street or block (e.g., Japanese) name.
+.TP
+%h
+House number or designation.
+.TP
+%N
+Insert an end-of-line if the previous descriptor's value was not an empty
+string; otherwise ignore.
+.TP
+%t
+Insert a space if the previous descriptor's value was not an empty string;
+otherwise ignore.
+.TP
+%r
+Room number, door designation.
+.TP
+%e
+Floor number.
+.TP
+%C
+Country designation, from the <country_post> keyword.
+.\" .TP
+.\" %l
+.\" BUG: %l escape sequence from ISO/IEC 14652:2002 is not
+.\" supported by glibc
+.\" Local township within town or city.
+.TP
+%z
+Zip number, postal code.
+.TP
+%T
+Town, city.
+.TP
+%S
+State, province, or prefecture.
+.TP
+%c
+Country, as taken from data record.
+.PP
+Each field descriptor may have an \(aqR\(aq after
+the \(aq%\(aq to specify that the
+information is taken from a Romanized version string of the
+entity.
+.RE
+
+.TP
+.I country_name
+followed by the country name in the language of the current document
+(e.g., "Deutschland" for the
+.IR de_DE
+locale).
+.TP
+.I country_post
+followed by the abbreviation of the country (see CERT_MAILCODES).
+.TP
+.I country_ab2
+followed by the two-letter abbreviation of the country (ISO 3166).
+.TP
+.I country_ab3
+followed by the three-letter abbreviation of the country (ISO 3166).
+.TP
+.I country_num
+followed by the numeric country code (ISO 3166).
+.TP
+.I country_car
+followed by the code for the country car number.
+.TP
+.I country_isbn
+followed by the ISBN code (for books).
+.TP
+.I lang_name
+followed by the language name in the language of the current document.
+.TP
+.I lang_ab
+followed by the two-letter abbreviation of the language (ISO 639).
+.TP
+.I lang_term
+followed by the three-letter abbreviation of the language (ISO 639-2/T).
+.TP
+.I lang_lib
+followed by the three-letter abbreviation of the language for library
+use (ISO 639-2/B).
+Applications should in general prefer
+.IR lang_term
+over
+.IR lang_lib .
+.PP
+The
+.B LC_ADDRESS
+definition ends with the string
+.IR "END LC_ADDRESS" .
.SS LC_CTYPE
-The definition for the
+The definition starts with the string
.B LC_CTYPE
-category starts with the string
-.I LC_CTYPE
in the first column.
-There are the following keywords allowed:
+The following keywords are allowed:
+.\" FIXME translit_start + translit_end are not documented
+.\" FIXME 'charclass' is not documented
+.\" FIXME 'charconv' is not documented
+.\" FIXME 'outdigit' is not documented
+.\" FIXME 'include' is not documented
+.\" FIXME 'map' (to_inpunct, to_outpunct) is not documented
.TP
.I upper
followed by a list of uppercase letters.
The
.B LC_CTYPE
definition ends with the string
-.IR "END LC_CYTPE" .
+.IR "END LC_CTYPE" .
.SS LC_COLLATE
+.\" FIXME: the description of LC_COLLATE lacks a lot of details
The
.B LC_COLLATE
category defines the rules for collating characters.
.B LC_COLLATE
in the first column.
-There are the following keywords allowed:
+The following keywords are allowed:
+.\" FIXME 'script' is not documented
+.\" FIXME 'symbol-equivalence' is not documented
.TP
.I collating-element
+followed by the definition of a collating-element symbol
+representing a multicharacter collating element.
.TP
.I collating-symbol
+followed by the definition of a collating symbol
+that can be used in collation order statements.
.PP
The order-definition starts with a line:
.TP
.I order_start
-.PP
-followed by a list of keywords out of
+followed by a list of keywords chosen from
.BR forward ,
.BR backward ,
or
.BR position .
The order definition consists of lines that describe the order
and is terminated with the keyword
-.TP
.IR order_end .
-.PP
-For more details see the sources in
-.I /usr/lib/nls/src
-notably the examples
-.BR POSIX ,
-.B Example
-and
-.B Example2
+.\" FIXME 'reorder-after' is not documented
+.\" FIXME 'reorder-end' is not documented
+.\" FIXME 'reorder-sections-after' is not documented
+.\" FIXME 'reorder-sections-end' is not documented
.PP
The
.B LC_COLLATE
definition ends with the string
.IR "END LC_COLLATE" .
+.SS LC_IDENTIFICATION
+This category contains meta-information about the locale definition.
+
+The definition starts with the string
+.B LC_IDENTIFICATION
+in the first column.
+
+The following keywords are allowed:
+.TP
+.I title
+followed by the title of the locale document
+(e.g., "Maori language locale for New Zealand").
+.TP
+.I source
+followed by the name of the organization that maintains this document.
+.TP
+.I address
+followed by the address of the organization that maintains this document.
+.TP
+.I contact
+followed by the name of the contact person at
+the organization that maintains this document.
+.TP
+.I email
+followed by the email address of the person or
+organization that maintains this document.
+.TP
+.I tel
+followed by the telephone number (in international format)
+of the organization that maintains this document.
+.TP
+.I fax
+followed by the fax number (in international format)
+of the organization that maintains this document.
+.TP
+.I language
+followed by the name of the language to which this document applies.
+.TP
+.I territory
+followed by the name of the country/geographic extent
+to which this document applies.
+.TP
+.I audience
+followed by a description of the audience for which this document is intended.
+.TP
+.I application
+followed by a description of any special application
+for which this document is intended.
+.TP
+.I abbreviation
+.\" as far as I can tell... (mtk)
+followed by the short name for this document.
+.TP
+.I revision
+followed by the revision number of this document.
+.TP
+.I date
+followed by the revision date of this document.
+.PP
+In addition, for each of the categories defined by the document,
+there should be a line starting with the keyword
+.IR category ,
+followed by:
+.IP * 3
+a string that identifies this locale category definition,
+.IP *
+a semicolon, and
+.IP *
+one of the
+.BI LC_ *
+identifiers.
+.PP
+The
+.B LC_IDENTIFICATION
+definition ends with the string
+.IR "END LC_IDENTIFICATION" .
+.SS LC_MESSAGES
+The definition starts with the string
+.B LC_MESSAGES
+in the first column.
+
+The following keywords are allowed:
+.TP
+.I yesexpr
+followed by a regular expression that describes possible
+yes-responses.
+.TP
+.I noexpr
+followed by a regular expression that describes possible
+no-responses.
+.TP
+.I yesstr
+followed by the output string corresponding to "yes".
+.TP
+.I nostr
+followed by the output string corresponding to "no".
+.PP
+The
+.B LC_MESSAGES
+definition ends with the string
+.IR "END LC_MESSAGES" .
+.SS LC_MEASUREMENT
+The definition starts with the string
+.B LC_MEASUREMENT
+in the first column.
+
+The following keywords are allowed:
+.TP
+.I measurement
+followed by number identifying the standard used for measurement.
+The following values are recognized:
+.RS
+.TP
+.B 1
+Metric.
+.TP
+.B 2
+US customary measurements.
+.RE
+.PP
+The
+.B LC_MEASUREMENT
+definition ends with the string
+.IR "END LC_MEASUREMENT" .
.SS LC_MONETARY
The definition starts with the string
.B LC_MONETARY
in the first column.
-There are the following keywords allowed:
+The following keywords are allowed:
.TP
.I int_curr_symbol
followed by the international currency symbol.
when formatting monetary quantities.
.TP
.I mon_grouping
-followed by a string that describes the formatting of numeric
-quantities.
+followed by a sequence of integers separated by semicolons that
+describe the formatting of monetary quantities.
+See
+.I grouping
+below for details.
.TP
.I positive_sign
followed by a string that is used to indicate a positive sign for
.I int_frac_digits
followed by the number of fractional digits that should be used when
formatting with the
-.BR int_curr_symbol .
+.IR int_curr_symbol .
.TP
.I frac_digits
followed by the number of fractional digits that should be used when
formatting with the
-.BR currency_symbol .
+.IR currency_symbol .
.TP
.I p_cs_precedes
-followed by an integer set to
-.B 1
-if the
+followed by an integer that indicates the placement of
.I currency_symbol
-or
-.I int_curr_symbol
-should precede the formatted monetary quantity or set to
-.B 0
-if the symbol succeeds the value.
-.TP
-.I p_sep_by_space
-followed by an integer.
+for a nonnegative formatted monetary quantity:
.RS
.TP
.B 0
-means that no space should be printed between the symbol and the
-value.
+the symbol succeeds the value.
.TP
.B 1
-means that a space should be printed between the symbol and the
-value.
-.TP
-.B 2
-means that a space should be printed between the symbol and the
-sign string, if adjacent.
+the symbol precedes the value.
.RE
.TP
.I n_cs_precedes
+followed by an integer that indicates the placement of
+.I currency_symbol
+for a negative formatted monetary quantity.
+The same values are recognized as for
+.IR p_cs_precedes .
+.TP
+.I int_p_cs_precedes
+followed by an integer that indicates the placement of
+.I int_currency_symbol
+for a nonnegative internationally formatted monetary quantity.
+The same values are recognized as for
+.IR p_cs_precedes .
+.TP
+.I int_n_cs_precedes
+followed by an integer that indicates the placement of
+.I int_currency_symbol
+for a negative internationally formatted monetary quantity.
+The same values are recognized as for
+.IR p_cs_precedes .
+.TP
+.I p_sep_by_space
+followed by an integer that indicates the separation of
+.IR currency_symbol ,
+the sign string, and the value for a nonnegative formatted monetary quantity.
+The following values are recognized:
.RS
.TP
.B 0
-- the symbol succeeds the value.
+No space separates the currency symbol and the value.
.TP
.B 1
-- the symbol precedes the value.
+If the currency symbol and the sign string are adjacent,
+a space separates them from the value;
+otherwise a space separates the currency symbol and the value.
+.TP
+.B 2
+If the currency symbol and the sign string are adjacent,
+a space separates them from the value;
+otherwise a space separates the sign string and the value.
.RE
.TP
.I n_sep_by_space
-An integer set to
-.B 0
-if no space separates the
-.I currency_symbol
-or
-.I int_curr_symbol
-from the value for a negative monetary quantity, set to
-.B 1
-if a space separates the symbol from the value and set to
-.B 2
-if a space separates the symbol and the sign string, if adjacent.
+followed by an integer that indicates the separation of
+.IR currency_symbol ,
+the sign string, and the value for a negative formatted monetary quantity.
+The same values are recognized as for
+.IR p_sep_by_space .
+.TP
+.I int_p_sep_by_space
+followed by an integer that indicates the separation of
+.IR int_currency_symbol ,
+the sign string,
+and the value for a nonnegative internationally formatted monetary quantity.
+The same values are recognized as for
+.IR p_sep_by_space .
+.TP
+.I int_n_sep_by_space
+followed by an integer that indicates the separation of
+.IR int_currency_symbol ,
+the sign string,
+and the value for a negative internationally formatted monetary quantity.
+The same values are recognized as for
+.IR p_sep_by_space .
.TP
.I p_sign_posn
+followed by an integer that indicates where the
+.I positive_sign
+should be placed for a nonnegative monetary quantity:
.RS
.TP
.B 0
.RE
.TP
.I n_sign_posn
+followed by an integer that indicates where the
+.I negative_sign
+should be placed for a negative monetary quantity.
+The same values are recognized as for
+.IR p_sign_posn .
+.TP
+.I int_p_sign_posn
+followed by an integer that indicates where the
+.I negative_sign
+should be placed for a nonnegative
+internationally formatted monetary quantity.
+The same values are recognized as for
+.IR p_sign_posn .
+.TP
+.I int_n_sign_posn
+followed by an integer that indicates where the
+.I negative_sign
+should be placed for a negative
+internationally formatted monetary quantity.
+The same values are recognized as for
+.IR p_sign_posn .
+.PP
+The
+.B LC_MONETARY
+definition ends with the string
+.IR "END LC_MONETARY" .
+.SS LC_NAME
+The definition starts with the string
+.B LC_NAME
+in the first column.
+
+Various keywords are allowed, but only
+.IR name_fmt
+is mandatory.
+Other keywords are needed only if there is common convention to
+use the corresponding salutation in this locale.
+The allowed keywords are as follows:
+.TP
+.I name_fmt
+followed by a string containing field descriptors that define
+the format used for names in the locale.
+The following field descriptors are recognized:
+.\" From localedata/locales/uk_UA:
.RS
.TP
-.B 0
-Parentheses enclose the quantity and the
-.I currency_symbol
-or
-.IR int_curr_symbol .
+%f
+Family name(s).
.TP
-.B 1
-The sign string precedes the quantity and the
-.I currency_symbol
-or the
-.IR int_curr_symbol .
+%F
+Family names in uppercase.
.TP
-.B 2
-The sign string succeeds the quantity and the
-.I currency_symbol
-or the
-.IR int_curr_symbol .
+%g
+First given name.
.TP
-.B 3
-The sign string precedes the
-.I currency_symbol
-or the
-.IR int_curr_symbol .
+%G
+First given initial.
.TP
-.B 4
-The sign string succeeds the
-.I currency_symbol
-or the
-.IR int_curr_symbol .
+%l
+First given name with Latin letters.
+.TP
+%o
+Other shorter name.
+.TP
+%m
+Additional given name(s).
+.TP
+%M
+Initials for additional given name(s).
+.TP
+%p
+Profession.
+.TP
+%s
+Salutation, such as "Doctor".
+.TP
+%S
+Abbreviated salutation, such as "Mr." or "Dr.".
+.TP
+%d
+Salutation, using the FDCC-sets conventions.
+.\" 1 for the name_gen
+.\" In glibc 2.19, %d1 is used in only:
+.\" /home/mtk/ARCHIVE/GLIBC/glibc-2.19/localedata/locales/bem_ZM
+.\" /home/mtk/ARCHIVE/GLIBC/glibc-2.19/localedata/locales/zh_HK
+.\" In glibc 2.19, %d[2-5] appear to be not used at all
+.\" 2 for name_mr
+.\" 3 for name_mrs
+.\" 4 for name_miss
+.\" 5 for name_ms
+.TP
+%t
+If the preceding field descriptor resulted in an empty string,
+then the empty string, otherwise a space character.
.RE
+.TP
+.I name_gen
+followed by the general salutation for any gender.
+.TP
+.I name_mr
+followed by the salutation for men.
+.TP
+.I name_mrs
+followed by the salutation for married women.
+.TP
+.I name_miss
+followed by the salutation for unmarried women.
+.TP
+.I name_ms
+followed by the salutation valid for all women.
.PP
The
-.B LC_MONETARY
+.B LC_NAME
definition ends with the string
-.IR "END LC_MONETARY" .
+.IR "END LC_NAME" .
.SS LC_NUMERIC
The definition starts with the string
.B LC_NUMERIC
when formatting numeric quantities.
.TP
.I grouping
-followed by a string that describes the formatting of numeric
-quantities.
+followed by a sequence of integers separated by semicolons that
+describe the formatting of numeric quantities.
+.IP
+Each integer specifies the number of digits in a group.
+The first integer defines the size of the group immediately
+to the left of the decimal delimiter.
+Subsequent integers define succeeding groups to the
+left of the previous group.
+If the last integer is not \-1, then the size of the previous group
+(if any) is repeatedly used for the remainder of the digits.
+If the last integer is \-1, then no further grouping is performed.
.PP
The
.B LC_NUMERIC
definition ends with the string
.IR "END LC_NUMERIC" .
+.SS LC_PAPER
+The definition starts with the string
+.B LC_PAPER
+in the first column.
+
+The following keywords are allowed:
+.TP
+.I height
+followed by the height, in millimeters, of the standard paper format.
+.TP
+.I width
+followed by the width, in millimeters, of the standard paper format.
+.PP
+The
+.B LC_PAPER
+definition ends with the string
+.IR "END LC_PAPER" .
+.SS LC_TELEPHONE
+The definition starts with the string
+.B LC_TELEPHONE
+in the first column.
+
+The following keywords are allowed:
+.TP
+.I tel_int_fmt
+followed by a string that contains field descriptors that identify
+the format used to dial international numbers.
+The following field descriptors are recognized:
+.\" From localedata/locales/uk_UA
+.RS
+.TP
+%a
+Area code without nationwide prefix (the prefix is often "00").
+.TP
+%A
+Area code including nationwide prefix.
+.TP
+%l
+Local number (within area code).
+.TP
+%e
+Extension (to local number).
+.TP
+%c
+Country code.
+.TP
+%C
+Alternate carrier service code used for dialing abroad.
+.TP
+%t
+If the preceding field descriptor resulted in an empty string,
+then the empty string, otherwise a space character.
+.RE
+.TP
+.I tel_dom_fmt
+followed by a string that contains field descriptors that identify
+the format used to dial domestic numbers.
+The recognized field descriptors are the same as for
+.IR tel_int_fmt .
+.TP
+.I int_select
+followed by the prefix used to call international phone numbers.
+.TP
+.I int_prefix
+followed by the prefix used from other countries to dial this country.
+.PP
+The
+.B LC_TELEPHONE
+definition ends with the string
+.IR "END LC_TELEPHONE" .
.SS LC_TIME
The definition starts with the string
.B LC_TIME
in the first column.
The following keywords are allowed:
+.\" FIXME 'era', 'era_d_fmt', 'era_d_t_fmt', 'era_t_fmt', are not documented
+.\" FIXME 'timezone' is not documented
.TP
.I abday
-followed by a list of abbreviated weekday names.
+followed by a list of abbreviated names of the days of the week.
The list starts with the first day of the week
as specified by
.I week
(Sunday by default).
.TP
.I day
-followed by a list of weekday names.
+followed by a list of names of the days of the week.
The list starts with the first day of the week
as specified by
.I week
followed by a list of month names.
.TP
.I am_pm
-The appropriate representation of the
+followed by the appropriate representation of the
.B am
and
.B pm
strings.
+This should be defined only for locales using AM/PM convention.
.TP
.I d_t_fmt
-The appropriate date and time format.
+followed by the appropriate date and time format.
.TP
.I d_fmt
-The appropriate date format.
+followed by the appropriate date format.
.TP
.I t_fmt
-The appropriate time format.
+followed by the appropriate time format.
.TP
.I t_fmt_ampm
-The appropriate time format when using 12h clock format.
+followed by the appropriate time format when using 12h clock format.
+This should be defined only for locales using the AM/PM convention.
.TP
.I week
followed by a list of three values:
list.
.TP
.IR first_weekday " (since glibc 2.2)"
-Number of the first day from the
+followed by the number of the first day from the
.I day
list to be shown in calendar applications.
The default value of
list item.
.TP
.IR first_workday " (since glibc 2.2)"
-Number of the first working day from the
+followed by the number of the first working day from the
.I day
list.
+The default value is
+.BR 2 .
+.TP
+.I cal_direction
+.\" from localedata/locales/uk_UA
+followed by a value that indicates the direction for the
+display of calendar dates, as follows:
+.RS
+.TP
+.B 1
+Left-right from top.
+.TP
+.B 2
+Top-down from left.
+.TP
+.B 3
+Right-left from top.
+.RE
+.TP
+.I date_fmt
+followed by the appropriate date representation for
+.BR date (1).
.PP
The
.B LC_TIME
definition ends with the string
.IR "END LC_TIME" .
-.SS LC_MESSAGES
-The definition starts with the string
-.B LC_MESSAGES
-in the first column.
-
-The following keywords are allowed:
+.SH FILES
.TP
-.I yesexpr
-followed by a regular expression that describes possible
-yes-responses.
+.I /usr/lib/locale/locale-archive
+Usual default locale archive location.
.TP
-.I noexpr
-followed by a regular expression that describes possible
-no-responses.
-.PP
-The
-.B LC_MESSAGES
-definition ends with the string
-.IR "END LC_MESSAGES" .
-
-See the POSIX.2 standard for details.
-.SH FILES
-/usr/lib/locale/
-\(em database for the current locale setting of that category
-.br
-/usr/lib/nls/charmap/* \(em charmap-files
-.SH "CONFORMING TO"
-POSIX.2, ISO/IEC 14652.
+.I /usr/share/i18n/locales
+Usual default path for locale definition files.
+.SH CONFORMING TO
+POSIX.2, ISO/IEC TR 14652.
.SH BUGS
This manual page isn't complete.
.\" .SH AUTHOR
.\" Jochen Hein (Hein@Student.TU-Clausthal.de)
-.SH "SEE ALSO"
+.SH SEE ALSO
.BR locale (1),
.BR localedef (1),
.BR localeconv (3),
+.BR newlocale (3),
.BR setlocale (3),
-.BR charmap (5)
+.BR uselocale (3),
+.BR charmap (5),
+.BR locale (7)
+.SH COLOPHON
+This page is part of release 3.68 of the Linux
+.I man-pages
+project.
+A description of the project,
+information about reporting bugs,
+and the latest version of this page,
+can be found at
+\%http://www.kernel.org/doc/man\-pages/.
OSDN Git Service
