locale.html

posix标准英文,html格式

shall be written in the following format:</p>

<pre>
<tt>"%s=\"%s\"\n", &lt;</tt><i>keyword name</i><tt>&gt;, &lt;</tt><i>keyword value</i><tt>&gt;
</tt>
</pre>

<p>If the keyword was <b>charmap</b>, the name of the charmap (if any) that was specified via the <a href=
"../utilities/localedef.html"><i>localedef</i></a> <b>-f</b> option when the locale was created shall be written, with the word
<b>charmap</b> as &lt;<i>keyword&nbsp;name</i>&gt;.</p>

<p>If a value is numeric, it shall be written in one of the following formats:</p>

<pre>
<tt>"%s=%d\n", &lt;</tt><i>keyword name</i><tt>&gt;, &lt;</tt><i>keyword value</i><tt>&gt;
<br>
"%s=%c%o\n", &lt;</tt><i>keyword name</i><tt>&gt;, &lt;</tt><i>escape character</i><tt>&gt;, &lt;</tt><i>keyword value</i><tt>&gt;
<br>
"%s=%cx%x\n", &lt;</tt><i>keyword name</i><tt>&gt;, &lt;</tt><i>escape character</i><tt>&gt;, &lt;</tt><i>keyword value</i><tt>&gt;
</tt>
</pre>

<p>where the &lt;<i>escape&nbsp;character</i>&gt; is that identified by the <b>escape_char</b> keyword in the current locale; see
the Base Definitions volume of IEEE&nbsp;Std&nbsp;1003.1-2001, <a href="../basedefs/xbd_chap07.html#tag_07_03">Section 7.3, Locale
Definition</a>.</p>

<p>Compound keyword values (list entries) shall be separated in the output by semicolons. When included in keyword values, the
semicolon, the double-quote, the backslash, and any control character shall be preceded (escaped) with the escape character.</p>
</li>

<li>
<p>If the <b>-k</b> option is not specified, selected keyword values shall be written, each in the following format:</p>

<pre>
<tt>"%s\n", &lt;</tt><i>keyword value</i><tt>&gt;
</tt>
</pre>

<p>If the keyword was <b>charmap</b>, the name of the charmap (if any) that was specified via the <a href=
"../utilities/localedef.html"><i>localedef</i></a> <b>-f</b> option when the locale was created shall be written.</p>
</li>

<li>
<p>If the <b>-m</b> option is specified, then a list of all available charmaps shall be written, each in the format:</p>

<pre>
<tt>"%s\n", &lt;</tt><i>charmap</i><tt>&gt;
</tt>
</pre>

<p>where &lt;<i>charmap</i>&gt; is in a format suitable for use as the option-argument to the <a href=
"../utilities/localedef.html"><i>localedef</i></a> <b>-f</b> option.</p>
</li>
</ol>
</blockquote>

<h4><a name="tag_04_76_11"></a>STDERR</h4>

<blockquote>
<p>The standard error shall be used only for diagnostic messages.</p>
</blockquote>

<h4><a name="tag_04_76_12"></a>OUTPUT FILES</h4>

<blockquote>
<p>None.</p>
</blockquote>

<h4><a name="tag_04_76_13"></a>EXTENDED DESCRIPTION</h4>

<blockquote>
<p>None.</p>
</blockquote>

<h4><a name="tag_04_76_14"></a>EXIT STATUS</h4>

<blockquote>
<p>The following exit values shall be returned:</p>

<dl compact>
<dt>&nbsp;0</dt>

<dd>All the requested information was found and output successfully.</dd>

<dt>&gt;0</dt>

<dd>An error occurred.</dd>
</dl>
</blockquote>

<h4><a name="tag_04_76_15"></a>CONSEQUENCES OF ERRORS</h4>

<blockquote>
<p>Default.</p>
</blockquote>

<hr>
<div class="box"><em>The following sections are informative.</em></div>

<h4><a name="tag_04_76_16"></a>APPLICATION USAGE</h4>

<blockquote>
<p>If the <i>LANG</i> environment variable is not set or set to an empty value, or one of the <i>LC_*</i> environment variables is
set to an unrecognized value, the actual locales assumed (if any) are implementation-defined as described in the Base Definitions
volume of IEEE&nbsp;Std&nbsp;1003.1-2001, <a href="../basedefs/xbd_chap08.html">Chapter 8, Environment Variables</a>.</p>

<p>Implementations are not required to write out the actual values for keywords in the categories <i>LC_CTYPE</i> and <i>LC_COLLATE
;</i> however, they must write out the categories (allowing an application to determine, for example, which character classes are
available).</p>
</blockquote>

<h4><a name="tag_04_76_17"></a>EXAMPLES</h4>

<blockquote>
<p>In the following examples, the assumption is that locale environment variables are set as follows:</p>

<pre>
<tt>LANG=locale_x
LC_COLLATE=locale_y
</tt>
</pre>

<p>The command <i>locale</i> would result in the following output:</p>

<pre>
<tt>LANG=locale_x
LC_CTYPE="locale_x"
LC_COLLATE=locale_y
LC_TIME="locale_x"
LC_NUMERIC="locale_x"
LC_MONETARY="locale_x"
LC_MESSAGES="locale_x"
LC_ALL=
</tt>
</pre>

<p>The order of presentation of the categories is not specified by this volume of IEEE&nbsp;Std&nbsp;1003.1-2001.</p>

<p>The command:</p>

<pre>
<tt>LC_ALL=POSIX locale -ck decimal_point
</tt>
</pre>

<p>would produce:</p>

<pre>
<tt>LC_NUMERIC
decimal_point="."
</tt>
</pre>

<p>The following command shows an application of <i>locale</i> to determine whether a user-supplied response is affirmative:</p>

<pre>
<tt>if printf "%s\n" "$response" | grep -Eq "$(locale yesexpr)"
then
    affirmative processing goes here
else
    non-affirmative processing goes here
fi
</tt>
</pre>
</blockquote>

<h4><a name="tag_04_76_18"></a>RATIONALE</h4>

<blockquote>
<p>The output for categories <i>LC_CTYPE</i> and <i>LC_COLLATE</i> has been made implementation-defined because there is a
questionable value in having a shell script receive an entire array of characters. It is also difficult to return a logical
collation description, short of returning a complete <a href="../utilities/localedef.html"><i>localedef</i></a> source.</p>

<p>The <b>-m</b> option was included to allow applications to query for the existence of charmaps. The output is a list of the
charmaps (implementation-supplied and user-supplied, if any) on the system.</p>

<p>The <b>-c</b> option was included for readability when more than one category is selected (for example, via more than one
keyword name or via a category name). It is valid both with and without the <b>-k</b> option.</p>

<p>The <b>charmap</b> keyword, which returns the name of the charmap (if any) that was used when the current locale was created,
was included to allow applications needing the information to retrieve it.</p>
</blockquote>

<h4><a name="tag_04_76_19"></a>FUTURE DIRECTIONS</h4>

<blockquote>
<p>None.</p>
</blockquote>

<h4><a name="tag_04_76_20"></a>SEE ALSO</h4>

<blockquote>
<p><a href="localedef.html"><i>localedef</i></a>, the Base Definitions volume of IEEE&nbsp;Std&nbsp;1003.1-2001, <a href=
"../basedefs/xbd_chap07.html#tag_07_03">Section 7.3, Locale Definition</a></p>
</blockquote>

<h4><a name="tag_04_76_21"></a>CHANGE HISTORY</h4>

<blockquote>
<p>First released in Issue 4.</p>
</blockquote>

<h4><a name="tag_04_76_22"></a>Issue 5</h4>

<blockquote>
<p>The FUTURE DIRECTIONS section is added.</p>
</blockquote>

<h4><a name="tag_04_76_23"></a>Issue 6</h4>

<blockquote>
<p>The normative text is reworded to avoid use of the term &quot;must&quot; for application requirements.</p>

<p>IEEE&nbsp;Std 1003.1-2001/Cor&nbsp;1-2002, item XCU/TC1/D6/30 is applied, correcting an editorial error in the STDOUT
section.</p>
</blockquote>

<div class="box"><em>End of informative text.</em></div>

<hr size="2" noshade>
<center><font size="2"><!--footer start-->
UNIX &reg; is a registered Trademark of The Open Group.<br>
POSIX &reg; is a registered Trademark of The IEEE.<br>
[ <a href="../mindex.html">Main Index</a> | <a href="../basedefs/contents.html">XBD</a> | <a href=
"../utilities/contents.html">XCU</a> | <a href="../functions/contents.html">XSH</a> | <a href="../xrat/contents.html">XRAT</a>
]</font></center>

<!--footer end-->
<hr size="2" noshade>
</body>
</html>