Un outil pour savoir si une commande est posix - retour accueil
git clone git://bebou.netlib.re/isposix
Log | Files | Refs | README |
gettext.html (20734B)
1 <!-- Copyright 2001-2024 IEEE and The Open Group, All Rights Reserved -->
2 <!DOCTYPE HTML>
3 <html lang="en">
4 <head>
5 <meta name="generator" content="HTML Tidy for HTML5 for Linux version 5.8.0">
6 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
7 <link type="text/css" rel="stylesheet" href="style.css"><!-- Generated by The Open Group rhtm tool v1.2.4 -->
8 <!-- Copyright (c) 2001-2024 The Open Group, All Rights Reserved -->
9 <title>gettext</title>
10 </head>
11 <body bgcolor="white">
12 <div class="NAVHEADER">
13 <table summary="Header navigation table" class="nav" width="100%" border="0" cellpadding="0" cellspacing="0">
14 <tr class="nav">
15 <td class="nav" width="15%" align="left" valign="bottom"><a href="../utilities/getopts.html" accesskey="P"><<<
16 Previous</a></td>
17 <td class="nav" width="70%" align="center" valign="bottom"><a href="contents.html">Home</a></td>
18 <td class="nav" width="15%" align="right" valign="bottom"><a href="../utilities/grep.html" accesskey="N">Next >>></a></td>
19 </tr>
20 </table>
21 <hr align="left" width="100%"></div>
22 <script language="JavaScript" src="../jscript/codes.js"></script><basefont size="3">
23 <center><font size="2">The Open Group Base Specifications Issue 8<br>
24 IEEE Std 1003.1-2024<br>
25 Copyright © 2001-2024 The IEEE and The Open Group</font></center>
26 <hr size="2" noshade>
27 <a name="top" id="top"></a> <a name="gettext" id="gettext"></a> <a name="tag_20_54" id="tag_20_54"></a><!-- gettext -->
28 <h4 class="mansect"><a name="tag_20_54_01" id="tag_20_54_01"></a>NAME</h4>
29 <blockquote>gettext, ngettext — retrieve text string from messages object</blockquote>
30 <h4 class="mansect"><a name="tag_20_54_02" id="tag_20_54_02"></a>SYNOPSIS</h4>
31 <blockquote class="synopsis">
32 <p><code><tt>gettext</tt> <b>[</b><tt>-e|-E</tt><b>] [</b><tt>-d textdomain</tt><b>] [</b><i>textdomain</i><b>]</b> <i>msgid</i> <tt><br>
33 <br>
34 gettext</tt> <b>[</b><tt>-e|-E</tt><b>] [</b><tt>-n</tt><b>]</b> <tt>-s</tt> <b>[</b><tt>-d</tt> <i>textdomain</i><b>]</b>
35 <i>msgid</i><tt>...<br>
36 <br>
37 ngettext</tt> <b>[</b><tt>-e|-E</tt><b>] [</b><tt>-d</tt> <i>textdomain</i><b>] [</b><i>textdomain</i><b>]</b> <i>msgid
38 msgid_plural n</i> <tt><br></tt></code></p>
39 </blockquote>
40 <h4 class="mansect"><a name="tag_20_54_03" id="tag_20_54_03"></a>DESCRIPTION</h4>
41 <blockquote>
42 <p>The <i>gettext</i> and <i>ngettext</i> utilities shall write to standard output the message string(s) that would result from the
43 following calls to functions defined in the System Interfaces volume of POSIX.1-2024:</p>
44 <pre>
45 <tt>if (textdomainname == NULL || textdomainname[0] == '\0')
46 message_string = msgid;
47 else {
48 setlocale(LC_ALL, "");
49 if (textdomaindir != NULL)
50 bindtextdomain(textdomainname, textdomaindir);
51 if (msgid_plural == NULL)
52 message_string = dgettext(textdomainname, msgid);
53 else
54 message_string = dngettext(textdomainname, msgid, msgid_plural, n);
55 }
56 </tt></pre>
57 <p>where:</p>
58 <ul>
59 <li>
60 <p>The <i>textdomaindir</i> variable is a string containing the value of the <i>TEXTDOMAINDIR</i> environment variable, if set and
61 not empty, or is NULL otherwise.</p>
62 </li>
63 <li>
64 <p>The <i>textdomainname</i> variable is a string containing the text domain name obtained from, in decreasing order of
65 precedence:</p>
66 <ul>
67 <li>
68 <p>The optional operand <i>textdomain,</i> if present</p>
69 </li>
70 <li>
71 <p>The <b>-d</b> <i>textdomain</i> option, if specified</p>
72 </li>
73 <li>
74 <p>The <i>TEXTDOMAIN</i> environment variable, if set and not empty</p>
75 </li>
76 </ul>
77 <p>If the text domain name cannot be obtained from these sources, the <i>textdomainname</i> variable is NULL.</p>
78 </li>
79 <li>
80 <p>If the <b>-s</b> option of <i>gettext</i> is not specified and for the <i>ngettext</i> utility, the <i>msgid</i> variable is a
81 string containing:</p>
82 <ul>
83 <li>
84 <p>The value of the <i>msgid</i> operand, if the <b>-E</b> option is specified</p>
85 </li>
86 <li>
87 <p>The value of the <i>msgid</i> operand with C-language escape sequences processed (see below), if the <b>-e</b> option is
88 specified</p>
89 </li>
90 <li>
91 <p>The value of the <i>msgid</i> operand with C-language escape sequences optionally processed (see below), otherwise</p>
92 </li>
93 </ul>
94 </li>
95 <li>
96 <p>If the <b>-s</b> option of <i>gettext</i> is specified, the <i>msgid</i> variable is a string containing:</p>
97 <ul>
98 <li>
99 <p>The value of each <i>msgid</i> operand in turn, if the <b>-E</b> option is specified or neither the <b>-e</b> nor the <b>-E</b>
100 option is specified</p>
101 </li>
102 <li>
103 <p>The value of each <i>msgid</i> operand in turn with C-language escape sequences processed (see below), if the <b>-e</b> option
104 is specified</p>
105 </li>
106 </ul>
107 </li>
108 <li>
109 <p>For the <i>gettext</i> utility, the <i>msgid_plural</i> variable is NULL. For the <i>ngettext</i> utility, the
110 <i>msgid_plural</i> variable is a string containing:</p>
111 <ul>
112 <li>
113 <p>The value of the <i>msgid_plural</i> operand, if the <b>-E</b> option is specified</p>
114 </li>
115 <li>
116 <p>The value of the <i>msgid_plural</i> operand with C-language escape sequences processed (see below), if the <b>-e</b> option is
117 specified</p>
118 </li>
119 <li>
120 <p>The value of the <i>msgid_plural</i> operand with C-language escape sequences optionally processed (see below), otherwise</p>
121 </li>
122 </ul>
123 </li>
124 <li>
125 <p>For the <i>gettext</i> utility, the <i>n</i> variable is 1 (one). For the <i>ngettext</i> utility the <i>n</i> variable is the
126 <i>n</i> operand, parsed as an integer as if by using the <a href="../functions/strtoul.html"><i>strtoul</i>()</a> function with a
127 <i>base</i> argument of 10.</p>
128 </li>
129 </ul>
130 <p>When C-language escape sequences are processed, they shall be processed as specified for character string literals in the
131 ISO C standard, except that <i>universal-character-name</i> escape sequences need not be supported. Implementations may also
132 support a <backslash> <tt>'c'</tt> escape sequence; if supported, the <tt>'\c'</tt> and all characters following it shall be
133 removed and, if the <b>-s</b> option is specified, the behavior shall be as if the <b>-n</b> option is also specified.</p>
134 <p>For the <i>ngettext</i> utility, and for the <i>gettext</i> utility if the <b>-s</b> option is not specified, the resulting
135 message string shall be written to standard output. If the <b>-s</b> option of <i>gettext</i> is specified, the resulting message
136 string for each <i>msgid</i> shall be written to standard output with consecutive message strings separated by a single
137 <space> character and, if the <b>-n</b> option is not specified, a <newline> shall be written after the last message
138 string. If the <b>-s</b> and <b>-n</b> options are specified, the trailing <newline> shall be omitted.</p>
139 <p>Under conditions where the <i>textdomainname</i> variable in the above code would be NULL, these utilities may write a
140 diagnostic message to standard error and exit with non-zero status.</p>
141 </blockquote>
142 <h4 class="mansect"><a name="tag_20_54_04" id="tag_20_54_04"></a>OPTIONS</h4>
143 <blockquote>
144 <p>These utilities shall conform to XBD <a href="../basedefs/V1_chap12.html#tag_12_02"><i>12.2 Utility Syntax Guidelines</i></a>
145 .</p>
146 <p>The following options shall be supported:</p>
147 <dl compact>
148 <dd></dd>
149 <dt><b>-d </b><i>textdomain</i></dt>
150 <dd><br>
151 Retrieve the translated message from the domain <i>textdomain</i>, if <i>textdomain</i> is not specified as an operand.</dd>
152 <dt><b>-e</b></dt>
153 <dd>Process C-language escape sequences in <i>msgid</i> and <i>msgid_plural</i> operands.</dd>
154 <dt><b>-E</b></dt>
155 <dd>Do not process C-language escape sequences in <i>msgid</i> and <i>msgid_plural</i> operands.</dd>
156 </dl>
157 <p>The <i>gettext</i> utility shall also support the following options:</p>
158 <dl compact>
159 <dd></dd>
160 <dt><b>-n</b></dt>
161 <dd>Modify the behavior of the <b>-s</b> option such that a <newline> is not appended to the output.</dd>
162 <dt><b>-s</b></dt>
163 <dd>Separate the message strings obtained from each <i>msgid</i> operand with <space> characters in the output, and (if
164 <b>-n</b> is not also specified) append a <newline> to the output.</dd>
165 </dl>
166 <p>If neither of the mutually exclusive <b>-e</b> and <b>-E</b> options is specified, it is unspecified which is the default,
167 except that if the <b>-s</b> option of <i>gettext</i> is specified then <b>-E</b> shall be the default.</p>
168 </blockquote>
169 <h4 class="mansect"><a name="tag_20_54_05" id="tag_20_54_05"></a>OPERANDS</h4>
170 <blockquote>
171 <p>The following operands shall be supported:</p>
172 <dl compact>
173 <dd></dd>
174 <dt><i>textdomain</i></dt>
175 <dd>A text domain name used to retrieve the translated message. This shall override the specification by the <b>-d</b> option, if
176 present.</dd>
177 <dt><i>msgid</i></dt>
178 <dd>A key to retrieve the translated message.</dd>
179 <dt><i>msgid_plural</i></dt>
180 <dd>A default plural if no corresponding plural message can be found.</dd>
181 <dt><i>n</i></dt>
182 <dd>A non-negative decimal integer to be used as the <i>n</i> argument to <a href=
183 "../functions/dngettext.html"><i>dngettext</i>()</a> (see the DESCRIPTION).</dd>
184 </dl>
185 </blockquote>
186 <h4 class="mansect"><a name="tag_20_54_06" id="tag_20_54_06"></a>STDIN</h4>
187 <blockquote>
188 <p>Not used.</p>
189 </blockquote>
190 <h4 class="mansect"><a name="tag_20_54_07" id="tag_20_54_07"></a>INPUT FILES</h4>
191 <blockquote>
192 <p>The input files are messages object files (see <a href="../utilities/msgfmt.html#"><i>msgfmt</i></a> ).</p>
193 </blockquote>
194 <h4 class="mansect"><a name="tag_20_54_08" id="tag_20_54_08"></a>ENVIRONMENT VARIABLES</h4>
195 <blockquote>
196 <p>The following environment variables shall affect the execution of <i>gettext</i> and <i>ngettext</i>:</p>
197 <dl compact>
198 <dd></dd>
199 <dt><i>LANG</i></dt>
200 <dd>Provide a default value for the internationalization variables that are unset or null. (See XBD <a href=
201 "../basedefs/V1_chap08.html#tag_08_02"><i>8.2 Internationalization Variables</i></a> for the precedence of internationalization
202 variables used to determine the values of locale categories.)</dd>
203 <dt><i>LANGUAGE</i></dt>
204 <dd>Determine the location of messages objects <sup>[<a href="javascript:open_code('XSI')">XSI</a>]</sup> <img src=
205 "../images/opt-start.gif" alt="[Option Start]" border="0"> if <i>NLSPATH</i> is not set or the evaluation of <i>NLSPATH</i>
206 did not lead to a suitable messages object being found. <img src="../images/opt-end.gif" alt="[Option End]" border="0"></dd>
207 <dt><i>LC_ALL</i></dt>
208 <dd>If set to a non-empty string value, override the values of all the other internationalization variables.</dd>
209 <dt><i>LC_MESSAGES</i></dt>
210 <dd><br>
211 Determine the locale name used to locate messages objects, and the locale that should be used to affect the format and contents of
212 diagnostic messages written to standard error.</dd>
213 <dt><i>NLSPATH</i></dt>
214 <dd><sup>[<a href="javascript:open_code('XSI')">XSI</a>]</sup> <img src="../images/opt-start.gif" alt="[Option Start]" border="0">
215 Determine the location of messages objects and message catalogs. <img src="../images/opt-end.gif" alt="[Option End]" border=
216 "0"></dd>
217 <dt><i>TEXTDOMAIN</i></dt>
218 <dd><br>
219 Specify the text domain name. (See XBD <a href="../basedefs/V1_chap03.html#tag_03_386"><i>3.386 Text Domain</i></a> .)</dd>
220 <dt><i>TEXTDOMAINDIR</i></dt>
221 <dd><br>
222 Specify the pathname to the messages object hierarchy. <sup>[<a href="javascript:open_code('XSI')">XSI</a>]</sup> <img src=
223 "../images/opt-start.gif" alt="[Option Start]" border="0"> <i>NLSPATH</i> shall have precedence over <i>TEXTDOMAINDIR .</i>
224 <img src="../images/opt-end.gif" alt="[Option End]" border="0"></dd>
225 </dl>
226 </blockquote>
227 <h4 class="mansect"><a name="tag_20_54_09" id="tag_20_54_09"></a>ASYNCHRONOUS EVENTS</h4>
228 <blockquote>
229 <p>Default.</p>
230 </blockquote>
231 <h4 class="mansect"><a name="tag_20_54_10" id="tag_20_54_10"></a>STDOUT</h4>
232 <blockquote>
233 <p>See DESCRIPTION.</p>
234 </blockquote>
235 <h4 class="mansect"><a name="tag_20_54_11" id="tag_20_54_11"></a>STDERR</h4>
236 <blockquote>
237 <p>The standard error shall be used only for diagnostic messages.</p>
238 </blockquote>
239 <h4 class="mansect"><a name="tag_20_54_12" id="tag_20_54_12"></a>OUTPUT FILES</h4>
240 <blockquote>
241 <p>None.</p>
242 </blockquote>
243 <h4 class="mansect"><a name="tag_20_54_13" id="tag_20_54_13"></a>EXTENDED DESCRIPTION</h4>
244 <blockquote>
245 <p>None.</p>
246 </blockquote>
247 <h4 class="mansect"><a name="tag_20_54_14" id="tag_20_54_14"></a>EXIT STATUS</h4>
248 <blockquote>
249 <p>The following exit values shall be returned:</p>
250 <dl compact>
251 <dd></dd>
252 <dt> 0</dt>
253 <dd>Successful completion.</dd>
254 <dt>>0</dt>
255 <dd>An error occurred.</dd>
256 </dl>
257 </blockquote>
258 <h4 class="mansect"><a name="tag_20_54_15" id="tag_20_54_15"></a>CONSEQUENCES OF ERRORS</h4>
259 <blockquote>
260 <p>Default.</p>
261 </blockquote>
262 <hr>
263 <div class="box"><em>The following sections are informative.</em></div>
264 <h4 class="mansect"><a name="tag_20_54_16" id="tag_20_54_16"></a>APPLICATION USAGE</h4>
265 <blockquote>
266 <p>Since it is unspecified which of the <b>-e</b> or <b>-E</b> options is the default, except when the <b>-s</b> option of
267 <i>gettext</i> is specified, portable applications need to ensure that <b>-e</b>, <b>-E</b>, or (for <i>gettext</i>) <b>-s</b> is
268 specified whenever a <i>msgid</i> or <i>msgid_plural</i> operand contains, or might contain, a <backslash> character.</p>
269 <p>Note that, unless the <b>-s</b> option of <i>gettext</i> is specified without <b>-n</b>, the message(s) written to standard
270 output are not followed by a <newline>. (Therefore the output only ends with a <newline> if the last message ends with
271 one.)</p>
272 <p>Both <i>msgid</i> and <i>msgid_plural</i> should be properly quoted for the shell.</p>
273 </blockquote>
274 <h4 class="mansect"><a name="tag_20_54_17" id="tag_20_54_17"></a>EXAMPLES</h4>
275 <blockquote>
276 <p>The following examples assume that the following portable messages object source file (dot-po file) has been compiled to a valid
277 file <b>mail.mo</b> by the <a href="../utilities/msgfmt.html"><i>msgfmt</i></a> utility. See the EXTENDED DESCRIPTION section of
278 the <a href="../utilities/msgfmt.html"><i>msgfmt</i></a> utility for a description of the dot-po file format.</p>
279 <pre>
280 <tt>msgid ""
281 msgstr ""
282 "Content-Type: text/plain; charset=utf-8\n"
283 "Plural-Forms: nplurals=4; plural=n==1?0: (n>1&&n<=10)?1: (n==0)?2:3;\n"
284 <br>
285 msgid "recipient"
286 msgid_plural "recipients"
287 msgstr[0] "1 recipient"
288 msgstr[1] "2 to 10 recipients"
289 msgstr[2] "no recipients"
290 msgstr[3] "more than 10 recipients"
291 <br>
292 msgid "%d attachment\n"
293 msgid_plural "%d attachments\n"
294 msgstr[0] "1 (%d) attachment\n"
295 msgstr[1] "2 to 10 (%d) attachments\n"
296 msgstr[2] "no (%d) attachments\n"
297 msgstr[3] "more than 10 (%d) attachments\n"
298 </tt></pre>
299 <p>They also assume that <b>mail.mo</b> is installed in the directory that <i>gettext</i> and <i>ngettext</i> search for the
300 current locale. See the OPTIONS and ENVIRONMENT VARIABLES sections above and the description of <a href=
301 "../functions/gettext.html"><i>gettext</i>()</a> for details on how this search is performed.</p>
302 <p>The command</p>
303 <pre>
304 <tt>ngettext -d mail recipient recipients 0
305 </tt></pre>
306 <p>will write <tt>"no recipients"</tt>.</p>
307 <p>The command</p>
308 <pre>
309 <tt>ngettext -d mail recipient recipients 1
310 </tt></pre>
311 <p>will write <tt>"1 recipient"</tt>.</p>
312 <p>The command</p>
313 <pre>
314 <tt>ngettext -d mail recipient recipients 5
315 </tt></pre>
316 <p>will write <tt>"2 to 10 recipients"</tt>.</p>
317 <p>The command</p>
318 <pre>
319 <tt>ngettext -d mail recipient recipients 11
320 </tt></pre>
321 <p>will write <tt>"more than 10 recipients"</tt>.</p>
322 <p>The command</p>
323 <pre>
324 <tt>ngettext -d mail Call Calls 1
325 </tt></pre>
326 <p>will write <tt>"Call"</tt>. Note that <tt>"Call"</tt> is not in the messages object.</p>
327 <p>The command</p>
328 <pre>
329 <tt>ngettext -d mail Call Calls 0
330 </tt></pre>
331 <p>will write <tt>"Calls"</tt>.</p>
332 <p>The command</p>
333 <pre>
334 <tt>ngettext -d mail Call Calls 10
335 </tt></pre>
336 <p>will write <tt>"Calls"</tt>.</p>
337 <p>The command</p>
338 <pre>
339 <tt>ngettext -ed mail "%d attachment\n" "%d attachments\n" 1
340 </tt></pre>
341 <p>will write the same as</p>
342 <pre>
343 <tt>printf "1 (%%d) attachment\n"
344 </tt></pre>
345 <p>(i.e. <tt>"1 (%d) attachment"</tt> followed by a <newline> character). The output of <i>ngettext</i> can be used as a
346 format string for <a href="../utilities/printf.html"><i>printf</i></a>.</p>
347 <p>The command</p>
348 <pre>
349 <tt>printf "$(ngettext -ed mail "%d attachment\n" "%d attachments\n" 1)" 10
350 </tt></pre>
351 <p>will write the same as</p>
352 <pre>
353 <tt>printf "1 (%d) attachment\n" 10
354 </tt></pre>
355 <p>(i.e. <tt>"1 (10) attachment"</tt> followed by a <newline> character).</p>
356 <p>The command</p>
357 <pre>
358 <tt>ngettext -e -d mail "\tsubject\n" "\tsubjects\n" 0
359 </tt></pre>
360 <p>will write the same as</p>
361 <pre>
362 <tt>printf "\tsubjects\n"
363 </tt></pre>
364 <p>(i.e. a <tab> character, followed by <tt>"subjects"</tt> followed by a <newline> character). Note that
365 <tt>"\tsubject\n"</tt> is not in the messages object.</p>
366 <p>The command</p>
367 <pre>
368 <tt>printf "%s\n" "$(ngettext -E -d mail "subject" "subjects" 0)"
369 </tt></pre>
370 <p>will write the same as</p>
371 <pre>
372 <tt>printf "subjects\n"
373 </tt></pre>
374 <p>(i.e. <tt>"subjects"</tt> followed by a <newline> character). Note that <tt>"subject"</tt> is not in the messages
375 object.</p>
376 <p>The command</p>
377 <pre>
378 <tt>gettext -s -d mail "recipient"
379 </tt></pre>
380 <p>will write <tt>"1 recipient"</tt> followed by a <newline> character.</p>
381 <p>The command</p>
382 <pre>
383 <tt>gettext -s -n -d mail "recipient"
384 </tt></pre>
385 <p>will write <tt>"1 recipient"</tt> without a <newline> character.</p>
386 </blockquote>
387 <h4 class="mansect"><a name="tag_20_54_18" id="tag_20_54_18"></a>RATIONALE</h4>
388 <blockquote>
389 <p>Historical implementations did not support the <tt>'\a'</tt> C-language escape sequence. This standard requires it to be
390 supported for consistency with other utilities that support the table in XBD <a href="../basedefs/V1_chap05.html#tag_05"><i>5. File
391 Format Notation</i></a> .</p>
392 <p>Unlike other standard utilities, the behavior of <i>gettext</i> and <i>ngettext</i> is not undefined when <i>NLSPATH</i>
393 overrides the system default path; see XBD <a href="../basedefs/V1_chap08.html#tag_08_02"><i>8.2 Internationalization
394 Variables</i></a> . This is so that applications can use these utilities to obtain message strings from messages objects in other
395 locations. However, it also means that they need to be implemented in such a way that they do not do anything that would result in
396 undefined behavior when they need to write a diagnostic message. In particular, they should not use a string obtained from a
397 message catalog or a messages object as a format string (or should only do so after checking that the string contains the correct
398 conversions).</p>
399 </blockquote>
400 <h4 class="mansect"><a name="tag_20_54_19" id="tag_20_54_19"></a>FUTURE DIRECTIONS</h4>
401 <blockquote>
402 <p>None.</p>
403 </blockquote>
404 <h4 class="mansect"><a name="tag_20_54_20" id="tag_20_54_20"></a>SEE ALSO</h4>
405 <blockquote>
406 <p><a href="../utilities/msgfmt.html#"><i>msgfmt</i></a> , <a href="../utilities/printf.html#tag_20_96"><i>printf</i></a></p>
407 <p>XBD <a href="../basedefs/V1_chap07.html#tag_07"><i>7. Locale</i></a> , <a href="../basedefs/V1_chap08.html#tag_08"><i>8.
408 Environment Variables</i></a> , <a href="../basedefs/V1_chap12.html#tag_12_02"><i>12.2 Utility Syntax Guidelines</i></a></p>
409 <p>XSH <a href="../functions/gettext.html#tag_17_238"><i>gettext</i></a> , <a href=
410 "../functions/iconv.html#tag_17_248"><i>iconv</i></a> , <a href="../functions/setlocale.html#"><i>setlocale</i></a></p>
411 </blockquote>
412 <h4 class="mansect"><a name="tag_20_54_21" id="tag_20_54_21"></a>CHANGE HISTORY</h4>
413 <blockquote>
414 <p>First released in Issue 8.</p>
415 </blockquote>
416 <div class="box"><em>End of informative text.</em></div>
417 <hr>
418 <p> </p>
419 <a href="#top"><span class="topOfPage">return to top of page</span></a><br>
420 <hr size="2" noshade>
421 <center><font size="2">UNIX® is a registered Trademark of The Open Group.<br>
422 POSIX™ is a Trademark of The IEEE.<br>
423 Copyright © 2001-2024 The IEEE and The Open Group, All Rights Reserved<br>
424 [ <a href="../mindex.html">Main Index</a> | <a href="../basedefs/contents.html">XBD</a> | <a href=
425 "../functions/contents.html">XSH</a> | <a href="../utilities/contents.html">XCU</a> | <a href="../xrat/contents.html">XRAT</a>
426 ]</font></center>
427 <hr size="2" noshade>
428 <div class="NAVHEADER">
429 <table summary="Header navigation table" class="nav" width="100%" border="0" cellpadding="0" cellspacing="0">
430 <tr class="nav">
431 <td class="nav" width="15%" align="left" valign="bottom"><a href="../utilities/getopts.html" accesskey="P"><<<
432 Previous</a></td>
433 <td class="nav" width="70%" align="center" valign="bottom"><a href="contents.html">Home</a></td>
434 <td class="nav" width="15%" align="right" valign="bottom"><a href="../utilities/grep.html" accesskey="N">Next >>></a></td>
435 </tr>
436 </table>
437 <hr align="left" width="100%"></div>
438 </body>
439 </html>