+'\" t -*- coding: UTF-8 -*-
.\" 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>
.\" 2008-06-17 Petr Baudis <pasky@suse.cz>
.\" LC_TIME: Describe first_weekday and first_workday
.\"
-.TH LOCALE 5 2014-06-13 "Linux" "Linux User Manual"
+.TH LOCALE 5 2014-12-31 "Linux" "Linux User Manual"
.SH NAME
locale \- describes a locale definition file
.SH DESCRIPTION
If the category should be copied,
the only valid keyword in the definition is
.B copy
-followed by the name of the locale which should be copied.
+followed by the name of the locale in double quotes which should be
+copied.
+.PP
+When defining a category from scratch, all field descriptors and strings
+should be defined as Unicode code points in angle brackets, unless
+otherwise stated below.
+For example, "€" is to be presented as "<U20AC>", "%a" as
+"<U0025><U0061>", and "Monday" as
+"<U0053><U0075><U006E><U0064><U0061><U0079>".
+Values defined as Unicode code points must be in double quotes, plain
+number values are not quoted (but
+.BR LC_CTYPE
+and
+.BR LC_COLLATE
+follow special formatting, see the system-provided locale files for
+examples).
.SS Locale category sections
The following category sections are defined by POSIX:
.IP * 3
.B LC_PAPER
.IP *
.B LC_TELEPHONE
+.PP
+See
+.BR locale (7)
+for a more detailed description of each category.
+
.SS LC_ADDRESS
The definition starts with the string
.B LC_ADDRESS
.\" .B LC_NAME
.\" .I name_fmt
.\" keyword.
+.\"
+.\" https://sourceware.org/bugzilla/show_bug.cgi?id=16983
.TP
%a
Care of person, or organization.
.\" BUG: %l escape sequence from ISO/IEC 14652:2002 is not
.\" supported by glibc
.\" Local township within town or city.
+.\"
+.\" https://sourceware.org/bugzilla/show_bug.cgi?id=16983
.TP
%z
Zip number, postal code.
followed by the three-letter abbreviation of the country (ISO 3166).
.TP
.I country_num
-followed by the numeric country code (ISO 3166).
+followed by the numeric country code as plain numbers (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).
+followed by the ISBN code as plain numbers (for books).
.TP
.I lang_name
followed by the language name in the language of the current document.
definition ends with the string
.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.
-Due to
-limitations of libc not all POSIX-options are implemented.
+Due to limitations of glibc not all POSIX-options are implemented.
The definition starts with the string
.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 values in this category are defined as plain strings.
+
The following keywords are allowed:
.TP
.I title
.B LC_MONETARY
in the first column.
+Values for
+.IR int_curr_symbol ,
+.IR currency_symbol ,
+.IR mon_decimal_point ,
+.IR mon_thousands_sep ,
+.IR positive_sign ,
+and
+.IR negative_sign
+are defined as Unicode code points, the others as plain numbers.
+
The following keywords are allowed:
.TP
.I int_curr_symbol
when formatting numeric quantities.
.TP
.I grouping
-followed by a sequence of integers separated by semicolons that
-describe the formatting of numeric quantities.
+followed by a sequence of integers as plain numbers 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
.B LC_PAPER
in the first column.
+Values in this category are defined as plain numbers.
+
The following keywords are allowed:
.TP
.I height
This should be left empty for locales not using AM/PM convention.
.TP
.I week
-followed by a list of three values:
+followed by a list of three values as plain numbers:
The number of days in a week (by default 7),
a date of beginning of the week (by default corresponds to Sunday),
and the minimal length of the first week in year (by default 4).
list to be shown in calendar applications.
The default value of
.B 1
-corresponds to either Sunday or Monday depending
+(plain number) corresponds to either Sunday or Monday depending
on the value of the second
.I week
list item.
.I day
list.
The default value is
-.BR 2 .
+.BR 2
+(plain number).
See NOTES.
.TP
.I cal_direction
.\" from localedata/locales/uk_UA
-followed by a value that indicates the direction for the
+followed by a plain number value that indicates the direction for the
display of calendar dates, as follows:
.RS
.TP
.I day
lists appropriately, and set
.I first_weekday
+and
+.I first_workday
to
.B 1
or
.BR 2 ,
-depending on whether the week actually starts on Sunday or Monday
-for the locale.
+depending on whether the week and work week actually starts on Sunday or
+Monday for the locale.
.SH BUGS
This manual page isn't complete.
.\" .SH AUTHOR
.BR unicode (7),
.BR utf-8 (7)
.SH COLOPHON
-This page is part of release 3.75 of the Linux
+This page is part of release 3.76 of the Linux
.I man-pages
project.
A description of the project,
OSDN Git Service
