2 .\" Copyright (c) 1992, X/Open Company Limited All Rights Reserved Portions Copyright (c) 1995, Sun Microsystems, Inc. All Rights Reserved
3 .\" Sun Microsystems, Inc. gratefully acknowledges The Open Group for permission to reproduce portions of its copyrighted documentation. Original documentation from The Open Group can be obtained online at
4 .\" http://www.opengroup.org/bookstore/.
5 .\" The Institute of Electrical and Electronics Engineers and The Open Group, have given us permission to reprint portions of their documentation. In the following statement, the phrase "this text" refers to portions of the system documentation. Portions of this text are reprinted and reproduced in electronic form in the Sun OS Reference Manual, from IEEE Std 1003.1, 2004 Edition, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between these versions and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html.
6 .\" This notice shall appear on any product containing this material.
7 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
8 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
9 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
10 .TH LOCALE 1 "Dec 20, 1996"
12 locale \- get locale-specific information
16 \fBlocale\fR [\fB-a\fR | \fB-m\fR]
21 \fBlocale\fR [\fB-ck\fR] \fIname\fR...
27 The \fBlocale\fR utility writes information about the current locale
28 environment, or all public locales, to the standard output. For the purposes of
29 this section, a \fIpublic locale\fR is one provided by the implementation that
30 is accessible to the application.
33 When \fBlocale\fR is invoked without any arguments, it summarizes the current
34 locale environment for each locale category as determined by the settings of
35 the environment variables.
38 When invoked with operands, it writes values that have been assigned to the
39 keywords in the locale categories, as follows:
44 Specifying a keyword name selects the named keyword and the category containing
51 Specifying a category name selects the named category and all keywords in that
57 The following options are supported:
64 Writes information about all available public locales. The available locales
65 include \fBPOSIX\fR, representing the POSIX locale.
74 Writes the names of selected locale categories. The \fB-c\fR option increases
75 readability when more than one category is selected (for example, via more than
76 one keyword name or via a category name). It is valid both with and without the
86 Writes the names and values of selected keywords. The implementation may omit
87 values for some keywords; see OPERANDS.
96 Writes names of available charmaps; see \fBlocaledef\fR(1).
102 The following operand is supported:
109 The name of a locale category, the name of a keyword in a locale category, or
110 the reserved name \fBcharmap\fR. The named category or keyword will be selected
111 for output. If a single \fIname\fR represents both a locale category name and a
112 keyword name in the current locale, the results are unspecified; otherwise,
113 both category and keyword names can be specified as \fIname\fR operands, in any
119 \fBExample 1 \fRExamples of the locale utility
122 In the following examples, the assumption is that locale environment variables
128 LANG=locale_x LC_COLLATE=locale_y
135 The command \fBlocale\fR would result in the following output:
142 LC_NUMERIC="locale_x"
145 LC_MONETARY="locale_x"
146 LC_MESSAGES="locale_x"
159 \fBLC_ALL=POSIX locale -ck decimal_point\fR
179 The following command shows an application of \fBlocale\fR to determine whether
180 a user-supplied response is affirmative:
185 \fBif printf "%s\en" "$response" | /usr/bin/grep -Eq\e
188 affirmative processing goes here
190 non-affirmative processing goes here
196 .SH ENVIRONMENT VARIABLES
199 See \fBenviron\fR(5) for the descriptions of \fBLANG\fR, \fBLC_ALL\fR,
200 \fBLC_CTYPE\fR, \fBLC_MESSAGES\fR, and \fBNLSPATH\fR.
203 The \fBLANG\fR, \fBLC_*\fR, and \fBNLSPATH\fR environment variables must
204 specify the current locale environment to be written out. These environment
205 variables will be used if the \fB-a\fR option is not specified.
209 The following exit values are returned:
216 All the requested information was found and output successfully.
231 See \fBattributes\fR(5) for descriptions of the following attributes:
239 ATTRIBUTE TYPE ATTRIBUTE VALUE
243 Interface Stability Standard
249 \fBlocaledef\fR(1), \fBattributes\fR(5), \fBcharmap\fR(5), \fBenviron\fR(5),
250 \fBlocale\fR(5), \fBstandards\fR(5)
254 If \fBLC_CTYPE\fR or keywords in the category \fBLC_CTYPE\fR are specified,
255 only the values in the range \fB0x00\fR-\fB0x7f\fR are written out.
258 If \fBLC_COLLATE\fR or keywords in the category \fBLC_COLLATE\fR are specified,
259 no actual values are written out.