Print this page
12743 man page spelling mistakes
*** 41,56 ****
.\"
.\"
.\" Copyright (c) 1992, X/Open Company Limited. All Rights Reserved.
.\" Portions Copyright (c) 2003, Sun Microsystems, Inc. All Rights Reserved.
.\"
! .TH LOCALE 5 "April 9, 2016"
.SH NAME
locale \- subset of a user's environment that depends on language and cultural
conventions
.SH DESCRIPTION
- .LP
A \fBlocale\fR is the definition of the subset of a user's environment that
depends on language and cultural conventions. It is made up from one or more
categories. Each category is identified by its name and controls specific
aspects of the behavior of components of the system. Category names correspond
to the following environment variable names:
--- 41,55 ----
.\"
.\"
.\" Copyright (c) 1992, X/Open Company Limited. All Rights Reserved.
.\" Portions Copyright (c) 2003, Sun Microsystems, Inc. All Rights Reserved.
.\"
! .TH LOCALE 5 "May 16, 2020"
.SH NAME
locale \- subset of a user's environment that depends on language and cultural
conventions
.SH DESCRIPTION
A \fBlocale\fR is the definition of the subset of a user's environment that
depends on language and cultural conventions. It is made up from one or more
categories. Each category is identified by its name and controls specific
aspects of the behavior of components of the system. Category names correspond
to the following environment variable names:
*** 137,147 ****
.LP
the value of the corresponding environment variable is used. If the environment
variable is unset or is set to the empty string, the \fBsetlocale()\fR
function sets the appropriate environment.
.SS "Locale Definition"
- .LP
Locales can be described with the file format accepted by the \fBlocaledef\fR
utility.
.sp
.LP
The locale definition file must contain one or more locale category source
--- 136,145 ----
*** 339,349 ****
present, only characters defined in the charmap can be specified using octal,
decimal or hexadecimal constants. Symbolic names not present in the charmap
file can be specified and will be ignored, as specified under item 1 above.
.RE
.SS "LC_CTYPE"
- .LP
The \fBLC_CTYPE\fR category defines character classification, case conversion
and other character attributes. In addition, a series of characters can be
represented by three adjacent periods representing an ellipsis symbol
(\fB\&...\fR). The ellipsis specification is interpreted as meaning that all
values between the values preceding and following it represent valid
--- 337,346 ----
*** 717,727 ****
specified. If the \fBtolower\fR keyword is omitted from the locale definition,
the mapping will be the reverse mapping of the one specified for \fBtoupper\fR.
.RE
.SS "LC_COLLATE"
- .LP
The \fBLC_COLLATE\fR category provides a collation sequence definition for
numerous utilities (such as \fBsort\fR(1), \fBuniq\fR(1), and so forth),
regular expression matching (see \fBregex\fR(5)), and the \fBstrcoll\fR(3C),
\fBstrxfrm\fR(3C), \fBwcscoll\fR(3C), and \fBwcsxfrm\fR(3C) functions.
.sp
--- 714,723 ----
*** 742,752 ****
.TP
2.
\fBUser-defined ordering of collating elements\fR. Each collating element is
assigned a collation value defining its order in the character (or basic)
collation sequence. This ordering is used by regular expressions and pattern
! matching and, unless collation weights are explicity specified, also as the
collation weight to be used in sorting.
.RE
.RS +4
.TP
3.
--- 738,748 ----
.TP
2.
\fBUser-defined ordering of collating elements\fR. Each collating element is
assigned a collation value defining its order in the character (or basic)
collation sequence. This ordering is used by regular expressions and pattern
! matching and, unless collation weights are explicitly specified, also as the
collation weight to be used in sorting.
.RE
.RS +4
.TP
3.
*** 831,841 ****
.RS 21n
Specify the end of the collation-order statements.
.RE
.SS "collating-element \fIkeyword\fR"
- .LP
In addition to the collating elements in the character set, the
\fBcollating-element\fR keyword is used to define multi-character collating
elements. The syntax is:
.sp
.in +2
--- 827,836 ----
*** 866,876 ****
.br
.in +2
\fBcollating-element\fR <\fBll\fR> from "\fBll\fR"
.in -2
.SS "collating-symbol \fIkeyword\fR"
- .LP
This keyword will be used to define symbols for use in collation sequence
statements; that is, between the \fBorder_start\fR and the \fBorder_end\fR
keywords. The syntax is:
.sp
.in +2
--- 861,870 ----
*** 905,915 ****
The \fBcollating-symbol\fR keyword defines a symbolic name that can be
associated with a relative position in the character order sequence. While such
a symbolic name does not represent any collating element, it can be used as a
weight.
.SS "order_start \fIkeyword\fR"
- .LP
The \fBorder_start\fR keyword must precede collation order entries and also
defines the number of weights for this collation sequence definition and other
collation rules.
.sp
.LP
--- 899,908 ----
*** 985,995 ****
.sp
.LP
If no operands are specified, a single \fBforward\fR operand is assumed.
.SS "Collation Order"
- .LP
The \fBorder_start\fR keyword is followed by collating identifier entries. The
syntax for the collating element entries is:
.sp
.in +2
.nf
--- 978,987 ----
*** 1184,1197 ****
The multi-character collating element <\fBch\fR> is represented by the
collating symbol <\fBch\fR> and belongs to the same primary equivalence class
as the multi-character collating element <\fBCh\fR>.
.RE
.SS "order_end \fIkeyword\fR"
- .LP
The collating order entries must be terminated with an \fBorder_end\fR keyword.
.SS "LC_MONETARY"
- .LP
The \fBLC_MONETARY\fR category defines the rules and symbols that are used to
format monetary numeric information. This information is available through the
\fBlocaleconv\fR(3C) function
.sp
.LP
--- 1176,1187 ----
*** 1694,1704 ****
.sp
.LP
The entry \fBn/a\fR indicates that the value is not available in the POSIX
locale.
.SS "LC_NUMERIC"
- .LP
The \fBLC_NUMERIC\fR category defines the rules and symbols that will be used
to format non-monetary numeric information. This information is available
through the \fBlocaleconv\fR(3C) function.
.sp
.LP
--- 1684,1693 ----
*** 1793,1803 ****
.sp
.LP
The entry \fBn/a\fR indicates that the value is not available in the POSIX
locale.
.SS "LC_TIME"
- .LP
The \fBLC_TIME\fR category defines the interpretation of the field descriptors
supported by \fBdate\fR(1) and affects the behavior of the \fBstrftime\fR(3C),
\fBwcsftime\fR(3C), \fBstrptime\fR(3C), and \fBnl_langinfo\fR(3C) functions.
Because the interfaces for C-language access and locale definition differ
significantly, they are described separately. For locale definition, the
--- 1782,1791 ----
*** 2060,2070 ****
modifier indicates that the string corresponding to the value specified via the
field descriptor will be used instead of the value.
.RE
.SS "LC_TIME \fIC-language\fR Access"
- .LP
The following information can be accessed. These correspond to constants
defined in <\fBlanginfo.h\fR> and used as arguments to the
\fBnl_langinfo\fR(3C) function.
.sp
.ne 2
--- 2048,2057 ----
*** 2322,2332 ****
\fBera_d_t_fmt\fR \fBERA_D_T_FMT\fR \fB%Ec\fR
\fBalt_digits\fR \fBALT_DIGITS\fR \fB%O\fR
.TE
.SS "LC_TIME \fIGeneral\fR Information"
- .LP
Although certain of the field descriptors in the POSIX locale (such as the name
of the month) are shown with initial capital letters, this need not be the case
in other locales. Programs using these fields may need to adjust the
capitalization if the output is going to be used at the beginning of a
sentence.
--- 2309,2318 ----
*** 2360,2370 ****
On 7/4/1776, the \fB%x\fR field descriptor would result in "The 4th day of July
in 1776" while 7/14/1789 would come out as "The 14 day of July in 1789" The
above example is for illustrative purposes only. The \fB%O\fR modifier is
primarily intended to provide for Kanji or Hindi digits in \fBdate\fR formats.
.SS "LC_MESSAGES"
- .LP
The \fBLC_MESSAGES\fR category defines the format and values for affirmative
and negative responses.
.sp
.LP
The following keywords are recognized as part of the locale definition file.
--- 2346,2355 ----
*** 2453,2463 ****
.sp
.LP
In an application conforming to the SUSv3 standard, the information on
\fByesstr\fR and \fBnostr\fR is not available.
.SH SEE ALSO
- .LP
\fBdate\fR(1), \fBlocale\fR(1), \fBlocaledef\fR(1), \fBsort\fR(1), \fBtr\fR(1),
\fBuniq\fR(1), \fBlocaleconv\fR(3C), \fBnl_langinfo\fR(3C),
\fBsetlocale\fR(3C), \fBstrcoll\fR(3C), \fBstrftime\fR(3C), \fBstrptime\fR(3C),
\fBstrxfrm\fR(3C), \fBwcscoll\fR(3C), \fBwcsftime\fR(3C), \fBwcsxfrm\fR(3C),
\fBwctype\fR(3C), \fBattributes\fR(5), \fBcharmap\fR(5), \fBextensions\fR(5),
--- 2438,2447 ----