isposix

Un outil pour savoir si une commande est posix - retour accueil

git clone git://bebou.netlib.re/isposix
Log | Files | Refs | README |

date.html (21442B)


      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>date</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/cxref.html" accesskey="P">&lt;&lt;&lt;
     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/dd.html" accesskey="N">Next &gt;&gt;&gt;</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="date" id="date"></a> <a name="tag_20_30" id="tag_20_30"></a><!-- date -->
     28 <h4 class="mansect"><a name="tag_20_30_01" id="tag_20_30_01"></a>NAME</h4>
     29 <blockquote>date — write the date and time</blockquote>
     30 <h4 class="mansect"><a name="tag_20_30_02" id="tag_20_30_02"></a>SYNOPSIS</h4>
     31 <blockquote class="synopsis">
     32 <p><code><tt>date</tt> <b>[</b><tt>-u</tt><b>] [</b><tt>+</tt><i>format</i><b>]</b> <tt><br>
     33 <br></tt></code></p>
     34 <div class="box"><code><tt><sup>[<a href="javascript:open_code('XSI')">XSI</a>]</sup> <img src="../images/opt-start.gif" alt=
     35 "[Option Start]" border="0"> date</tt> <b>[</b><tt>-u</tt><b>]</b> <i>mmddhhmm</i><b>[[</b><i>cc</i><b>]</b><i>yy</i><b>]</b>
     36 <tt><img src="../images/opt-end.gif" alt="[Option End]" border="0"></tt></code></div>
     37 <tt><br></tt></blockquote>
     38 <h4 class="mansect"><a name="tag_20_30_03" id="tag_20_30_03"></a>DESCRIPTION</h4>
     39 <blockquote>
     40 <p>The <i>date</i> utility shall write the date and time to standard output <sup>[<a href=
     41 "javascript:open_code('XSI')">XSI</a>]</sup> <img src="../images/opt-start.gif" alt="[Option Start]" border="0"> &nbsp;or attempt
     42 to set the system date and time. <img src="../images/opt-end.gif" alt="[Option End]" border="0"> By default, the current date and
     43 time shall be written. If an operand beginning with <tt>'+'</tt> is specified, the output format of <i>date</i> shall be controlled
     44 by the conversion specifications and other text in the operand.</p>
     45 </blockquote>
     46 <h4 class="mansect"><a name="tag_20_30_04" id="tag_20_30_04"></a>OPTIONS</h4>
     47 <blockquote>
     48 <p>The <i>date</i> utility shall conform to XBD <a href="../basedefs/V1_chap12.html#tag_12_02"><i>12.2 Utility Syntax
     49 Guidelines</i></a> .</p>
     50 <p>The following option shall be supported:</p>
     51 <dl compact>
     52 <dd></dd>
     53 <dt><b>-u</b></dt>
     54 <dd>Perform operations as if the <i>TZ</i> environment variable was set to the string <tt>"UTC0"</tt>, or its equivalent historical
     55 value of <tt>"GMT0"</tt>. Otherwise, <i>date</i> shall use the timezone indicated by the <i>TZ</i> environment variable or the
     56 system default if that variable is unset or null.</dd>
     57 </dl>
     58 </blockquote>
     59 <h4 class="mansect"><a name="tag_20_30_05" id="tag_20_30_05"></a>OPERANDS</h4>
     60 <blockquote>
     61 <p>The following operands shall be supported:</p>
     62 <dl compact>
     63 <dd></dd>
     64 <dt>+<i>format</i></dt>
     65 <dd>When the format is specified, the output shall be formatted as if by <a href="../functions/strftime.html"><i>strftime</i>()</a>
     66 with the specified format string, and a <i>timeptr</i> argument that is the equivalent of <i>localtime</i>(&<i>now</i>) if
     67 <b>-u</b> is not specified or <i>gmtime</i>(&<i>now</i>) if <b>-u</b> is specified, where <i>now</i> is an object of type
     68 <b>time_t</b> containing the return value of <i>time</i>(0).
     69 <p>A &lt;newline&gt; shall always be appended to the output of <a href="../functions/strftime.html"><i>strftime</i>()</a>.</p>
     70 </dd>
     71 <dt><i>mmddhhmm</i><b>[[</b><i>cc</i><b>]</b><i>yy</i><b>]</b></dt>
     72 <dd><sup>[<a href="javascript:open_code('XSI')">XSI</a>]</sup> <img src="../images/opt-start.gif" alt="[Option Start]" border=
     73 "0"><br>
     74 Attempt to set the system date and time from the value given in the operand. This is only possible if the user has appropriate
     75 privileges and the system permits the setting of the system date and time. The first <i>mm</i> is the month (number); <i>dd</i> is
     76 the day (number); <i>hh</i> is the hour (number, 24-hour system); the second <i>mm</i> is the minute (number); <i>cc</i> is the
     77 century and is the first two digits of the year (this is optional); <i>yy</i> is the last two digits of the year and is optional.
     78 If century is not specified, then values in the range [69,99] shall refer to years 1969 to 1999 inclusive, and values in the range
     79 [00,68] shall refer to years 2000 to 2068 inclusive. The current year is the default if <i>yy</i> is omitted. <img src=
     80 "../images/opt-end.gif" alt="[Option End]" border="0"> <basefont size="2">
     81 <dl>
     82 <dt><b>Note:</b></dt>
     83 <dd>It is expected that in a future version of this standard the default century inferred from a 2-digit year will change. (This
     84 would apply to all commands accepting a 2-digit year as input.)</dd>
     85 </dl>
     86 <basefont size="3"></dd>
     87 </dl>
     88 </blockquote>
     89 <h4 class="mansect"><a name="tag_20_30_06" id="tag_20_30_06"></a>STDIN</h4>
     90 <blockquote>
     91 <p>Not used.</p>
     92 </blockquote>
     93 <h4 class="mansect"><a name="tag_20_30_07" id="tag_20_30_07"></a>INPUT FILES</h4>
     94 <blockquote>
     95 <p>None.</p>
     96 </blockquote>
     97 <h4 class="mansect"><a name="tag_20_30_08" id="tag_20_30_08"></a>ENVIRONMENT VARIABLES</h4>
     98 <blockquote>
     99 <p>The following environment variables shall affect the execution of <i>date</i>:</p>
    100 <dl compact>
    101 <dd></dd>
    102 <dt><i>LANG</i></dt>
    103 <dd>Provide a default value for the internationalization variables that are unset or null. (See XBD <a href=
    104 "../basedefs/V1_chap08.html#tag_08_02"><i>8.2 Internationalization Variables</i></a> for the precedence of internationalization
    105 variables used to determine the values of locale categories.)</dd>
    106 <dt><i>LC_ALL</i></dt>
    107 <dd>If set to a non-empty string value, override the values of all the other internationalization variables.</dd>
    108 <dt><i>LC_CTYPE</i></dt>
    109 <dd>Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as
    110 opposed to multi-byte characters in arguments).</dd>
    111 <dt><i>LC_MESSAGES</i></dt>
    112 <dd><br>
    113 Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error.</dd>
    114 <dt><i>LC_TIME</i></dt>
    115 <dd>Determine the format and contents of date and time strings written by <i>date</i>.</dd>
    116 <dt><i>NLSPATH</i></dt>
    117 <dd><sup>[<a href="javascript:open_code('XSI')">XSI</a>]</sup> <img src="../images/opt-start.gif" alt="[Option Start]" border="0">
    118 Determine the location of messages objects and message catalogs. <img src="../images/opt-end.gif" alt="[Option End]" border=
    119 "0"></dd>
    120 <dt><i>TZ</i></dt>
    121 <dd>Determine the timezone in which the time and date are written, unless the <b>-u</b> option is specified. If the <i>TZ</i>
    122 variable is unset or null and <b>-u</b> is not specified, an unspecified system default timezone is used.</dd>
    123 </dl>
    124 </blockquote>
    125 <h4 class="mansect"><a name="tag_20_30_09" id="tag_20_30_09"></a>ASYNCHRONOUS EVENTS</h4>
    126 <blockquote>
    127 <p>Default.</p>
    128 </blockquote>
    129 <h4 class="mansect"><a name="tag_20_30_10" id="tag_20_30_10"></a>STDOUT</h4>
    130 <blockquote>
    131 <p>When no formatting operand is specified, the output in the POSIX locale shall be equivalent to specifying:</p>
    132 <pre>
    133 <tt>date "+%a %b %e %H:%M:%S %Z %Y"
    134 </tt></pre></blockquote>
    135 <h4 class="mansect"><a name="tag_20_30_11" id="tag_20_30_11"></a>STDERR</h4>
    136 <blockquote>
    137 <p>The standard error shall be used only for diagnostic messages.</p>
    138 </blockquote>
    139 <h4 class="mansect"><a name="tag_20_30_12" id="tag_20_30_12"></a>OUTPUT FILES</h4>
    140 <blockquote>
    141 <p>None.</p>
    142 </blockquote>
    143 <h4 class="mansect"><a name="tag_20_30_13" id="tag_20_30_13"></a>EXTENDED DESCRIPTION</h4>
    144 <blockquote>
    145 <p>None.</p>
    146 </blockquote>
    147 <h4 class="mansect"><a name="tag_20_30_14" id="tag_20_30_14"></a>EXIT STATUS</h4>
    148 <blockquote>
    149 <p>The following exit values shall be returned:</p>
    150 <dl compact>
    151 <dd></dd>
    152 <dt>&nbsp;0</dt>
    153 <dd>The date was written successfully.</dd>
    154 <dt>&gt;0</dt>
    155 <dd>An error occurred.</dd>
    156 </dl>
    157 </blockquote>
    158 <h4 class="mansect"><a name="tag_20_30_15" id="tag_20_30_15"></a>CONSEQUENCES OF ERRORS</h4>
    159 <blockquote>
    160 <p>Default.</p>
    161 </blockquote>
    162 <hr>
    163 <div class="box"><em>The following sections are informative.</em></div>
    164 <h4 class="mansect"><a name="tag_20_30_16" id="tag_20_30_16"></a>APPLICATION USAGE</h4>
    165 <blockquote>
    166 <p>Conversion specifiers are of unspecified format when not in the POSIX locale. Some of them can contain &lt;newline&gt;
    167 characters in some locales, so it may be difficult to use the format shown in standard output for parsing the output of <i>date</i>
    168 in those locales.</p>
    169 <p>Since the default <i>date</i> utility format for locales other than the POSIX or C locale is not required to include anything
    170 beyond the date and time, whereas for the POSIX or C locale it also includes the day name and time zone, it may be necessary to
    171 specify a format (or override the locale-selection environment variables) to ensure this information is included when desired.</p>
    172 <p>The range of values for <tt>%S</tt> extends from 0 to 60 seconds to accommodate the occasional leap second.</p>
    173 <p>Although certain of the conversion specifiers in the POSIX locale (such as the name of the month) are shown with initial capital
    174 letters, this need not be the case in other locales. Programs using these fields may need to adjust the capitalization if the
    175 output is going to be used at the beginning of a sentence.</p>
    176 <p>The date string formatting capabilities are intended for use in Gregorian-style calendars, possibly with a different starting
    177 year (or years). The <tt>%x</tt> and <tt>%c</tt> conversion specifications, however, are intended for local representation; these
    178 may be based on a different, non-Gregorian calendar.</p>
    179 <p>The <tt>%C</tt> conversion specification was introduced to allow a fallback for the <tt>%EC</tt> (alternative year format base
    180 year); it can be viewed as the base of the current subdivision in the Gregorian calendar. The century number is calculated as the
    181 year divided by 100 and truncated to an integer; it should not be confused with the use of ordinal numbers for centuries (for
    182 example, &quot;twenty-first century&quot;.) Both the <tt>%Ey</tt> and <tt>%y</tt> can then be viewed as the offset from <tt>%EC</tt> and
    183 <tt>%C</tt>, respectively.</p>
    184 <p>The <tt>E</tt> and <tt>O</tt> modifiers modify the traditional conversion specifiers, so that they can always be used, even if
    185 the implementation (or the current locale) does not support the modifier.</p>
    186 <p>The <tt>E</tt> modifier supports alternative date formats, such as the Japanese Emperor's Era, as long as these are based on the
    187 Gregorian calendar system. Extending the <tt>E</tt> modifiers to other date elements may provide an implementation-defined
    188 extension capable of supporting other calendar systems, especially in combination with the <tt>O</tt> modifier.</p>
    189 <p>The <tt>O</tt> modifier supports time and date formats using the locale's alternative numerical symbols, such as Kanji or Hindi
    190 digits or ordinal number representation.</p>
    191 <p>Non-European locales, whether they use Latin digits in computational items or not, often have local forms of the digits for use
    192 in date formats. This is not totally unknown even in Europe; a variant of dates uses Roman numerals for the months: the third day
    193 of September 1991 would be written as 3.IX.1991. In Japan, Kanji digits are regularly used for dates; in Arabic-speaking countries,
    194 Hindi digits are used. The <tt>%d</tt>, <tt>%e</tt>, <tt>%H</tt>, <tt>%I</tt>, <tt>%m</tt>, <tt>%S</tt>, <tt>%U</tt>, <tt>%w</tt>,
    195 <tt>%W</tt>, and <tt>%y</tt> conversion specifications always return the date and time field in Latin digits (that is, 0 to 9). The
    196 <tt>%O</tt> modifier was introduced to support the use for display purposes of non-Latin digits. In the <i>LC_TIME</i> category in
    197 <a href="../utilities/localedef.html"><i>localedef</i></a>, the optional <b>alt_digits</b> keyword is intended for this purpose. As
    198 an example, assume the following (partial) <a href="../utilities/localedef.html"><i>localedef</i></a> source:</p>
    199 <pre>
    200 <tt>alt_digits  "";"I";"II";"III";"IV";"V";"VI";"VII";"VIII" \
    201             "IX";"X";"XI";"XII"
    202 d_fmt       "%e.%Om.%Y"
    203 </tt></pre>
    204 <p>With the above date, the command:</p>
    205 <pre>
    206 <tt>date "+%x"
    207 </tt></pre>
    208 <p>would yield 3.IX.1991. With the same <b>d_fmt</b>, but without the <b>alt_digits</b>, the command would yield 3.9.1991.</p>
    209 </blockquote>
    210 <h4 class="mansect"><a name="tag_20_30_17" id="tag_20_30_17"></a>EXAMPLES</h4>
    211 <blockquote>
    212 <ol>
    213 <li>
    214 <p>The following are input/output examples of <i>date</i> used at arbitrary times in the POSIX locale:</p>
    215 <pre>
    216 <b>$ </b><tt>date
    217 </tt><b>Tue Jun 26 09:58:10 PDT 1990
    218 <br>
    219 $ </b><tt>date "+DATE: %m/%d/%y%nTIME: %H:%M:%S"
    220 </tt><b>DATE: 11/02/91
    221 TIME: 13:36:16
    222 <br>
    223 $ </b><tt>date "+TIME: %r"
    224 </tt><b>TIME: 01:36:32 PM</b><tt>
    225 </tt></pre></li>
    226 <li>
    227 <p>Examples for Denmark, where the default date and time format is <tt>%a</tt> <tt>%d</tt> <tt>%b</tt> <tt>%Y</tt> <tt>%T</tt>
    228 <tt>%Z</tt>:</p>
    229 <pre>
    230 <b>$ </b><tt>LANG=da_DK.iso_8859-1 date
    231 </tt><b>ons 02 okt 1991 15:03:32 CET
    232 <br>
    233 $ </b><tt>LANG=da_DK.iso_8859-1 \
    234     date "+DATO: %A den %e. %B %Y%nKLOKKEN: %H:%M:%S"
    235 </tt><b>DATO: onsdag den 2. oktober 1991
    236 KLOKKEN: 15:03:56</b><tt>
    237 </tt></pre></li>
    238 <li>
    239 <p>Examples for Germany, where the default date and time format is <tt>%a</tt> <tt>%d</tt>.<tt>%h</tt>.<tt>%Y</tt>, <tt>%T</tt>
    240 <tt>%Z</tt>:</p>
    241 <pre>
    242 <b>$ </b><tt>LANG=De_DE.88591 date
    243 </tt><b>Mi 02.Okt.1991, 15:01:21 MEZ
    244 <br>
    245 $ </b><tt>LANG=De_DE.88591 date "+DATUM: %A, %d. %B %Y%nZEIT: %H:%M:%S"
    246 </tt><b>DATUM: Mittwoch, 02. Oktober 1991
    247 ZEIT: 15:02:02</b><tt>
    248 </tt></pre></li>
    249 <li>
    250 <p>Examples for France, where the default date and time format is <tt>%a</tt> <tt>%d</tt> <tt>%h</tt> <tt>%Y</tt> <tt>%Z</tt>
    251 <tt>%T</tt>:</p>
    252 <pre>
    253 <b>$ </b><tt>LANG=Fr_FR.88591 date
    254 </tt><b>Mer 02 oct 1991 MET 15:03:32
    255 <br>
    256 $ </b><tt>LANG=Fr_FR.88591 date "+JOUR: %A %d %B %Y%nHEURE: %H:%M:%S"
    257 </tt><b>JOUR: Mercredi 02 octobre 1991
    258 HEURE: 15:03:56</b><tt>
    259 </tt></pre></li>
    260 </ol>
    261 </blockquote>
    262 <h4 class="mansect"><a name="tag_20_30_18" id="tag_20_30_18"></a>RATIONALE</h4>
    263 <blockquote>
    264 <p>Some of the new options for formatting are from the ISO&nbsp;C standard. The <b>-u</b> option was introduced to allow portable
    265 access to Coordinated Universal Time (UTC). The string <tt>"GMT0"</tt> is allowed as an equivalent <i>TZ</i> value to be compatible
    266 with all of the systems using the BSD implementation, where this option originated.</p>
    267 <p>The <tt>%e</tt> format conversion specification (adopted from System V) was added because the ISO&nbsp;C standard conversion
    268 specifications did not provide any way to produce the historical default <i>date</i> output during the first nine days of any
    269 month.</p>
    270 <p>There are two varieties of day and week numbering supported (in addition to any others created with the locale-dependent
    271 <tt>%E</tt> and <tt>%O</tt> modifier characters):</p>
    272 <ul>
    273 <li>
    274 <p>The historical variety in which Sunday is the first day of the week and the weekdays preceding the first Sunday of the year are
    275 considered week 0. These are represented by <tt>%w</tt> and <tt>%U</tt>. A variant of this is <tt>%W</tt>, using Monday as the
    276 first day of the week, but still referring to week 0. This view of the calendar was retained because so many historical
    277 applications depend on it and the ISO&nbsp;C standard <a href="../functions/strftime.html"><i>strftime</i>()</a> function, on which
    278 many <i>date</i> implementations are based, was defined in this way.</p>
    279 </li>
    280 <li>
    281 <p>The international standard, based on the ISO&nbsp;8601:2019 standard where Monday is the first weekday and the algorithm for the
    282 first week number is more complex: If the week (Monday to Sunday) containing January 1 has four or more days in the new year, then
    283 it is week 1; otherwise, it is week 53 of the previous year, and the next week is week 1. These are represented by the new
    284 conversion specifications <tt>%u</tt> and <tt>%V</tt>, added as a result of international comments.</p>
    285 </li>
    286 </ul>
    287 <p>Although this standard only requires the default <i>date</i> utility format, for locales other than the POSIX or C locale, to
    288 include the date and time, it is common for implementations to include day name and time zone information as well. (For the POSIX
    289 locale this is required, with the day name in <tt>%a</tt> format at the beginning and the time zone in <tt>%Z</tt> format before
    290 the year.) Implementations are encouraged to include the day name (in <tt>%a</tt> or <tt>%A</tt> format) and the time zone (in
    291 <tt>%Z</tt> or <tt>%z</tt> format) in the default <i>date</i> utility format for all of the locales they provide.</p>
    292 <p>Some implementations have a <b>date_fmt</b> locale keyword (see <a href="../basedefs/V1_chap07.html#tag_07_03_05"><i>7.3.5
    293 LC_TIME</i></a> ) as an extension, to specify the default <i>date</i> utility format for each locale. On such implementations, if
    294 the <a href="../utilities/localedef.html"><i>localedef</i></a> utility is used to create a locale that does not have this
    295 information, the <i>date</i> utility must by default still produce output for that locale that includes both the time and the
    296 date.</p>
    297 </blockquote>
    298 <h4 class="mansect"><a name="tag_20_30_19" id="tag_20_30_19"></a>FUTURE DIRECTIONS</h4>
    299 <blockquote>
    300 <p>None.</p>
    301 </blockquote>
    302 <h4 class="mansect"><a name="tag_20_30_20" id="tag_20_30_20"></a>SEE ALSO</h4>
    303 <blockquote>
    304 <p>XBD <a href="../basedefs/V1_chap07.html#tag_07_03_05"><i>7.3.5 LC_TIME</i></a> , <a href=
    305 "../basedefs/V1_chap08.html#tag_08"><i>8. Environment Variables</i></a> , <a href="../basedefs/V1_chap12.html#tag_12_02"><i>12.2
    306 Utility Syntax Guidelines</i></a></p>
    307 <p>XSH <a href="../functions/fprintf.html#"><i>fprintf</i></a> , <a href="../functions/strftime.html#"><i>strftime</i></a></p>
    308 </blockquote>
    309 <h4 class="mansect"><a name="tag_20_30_21" id="tag_20_30_21"></a>CHANGE HISTORY</h4>
    310 <blockquote>
    311 <p>First released in Issue 2.</p>
    312 </blockquote>
    313 <h4 class="mansect"><a name="tag_20_30_22" id="tag_20_30_22"></a>Issue 5</h4>
    314 <blockquote>
    315 <p>Changes are made for Year 2000 alignment.</p>
    316 </blockquote>
    317 <h4 class="mansect"><a name="tag_20_30_23" id="tag_20_30_23"></a>Issue 6</h4>
    318 <blockquote>
    319 <p>The following new requirements on POSIX implementations derive from alignment with the Single UNIX Specification:</p>
    320 <ul>
    321 <li>
    322 <p>The <tt>%EX</tt> modified conversion specification is added.</p>
    323 </li>
    324 </ul>
    325 <p>The Open Group Corrigendum U048/2 is applied, correcting the examples.</p>
    326 <p>The DESCRIPTION is updated to refer to conversion specifications, instead of field descriptors for consistency with the
    327 <i>LC_TIME</i> category.</p>
    328 <p>A clarification is made such that the current year is the default if the <i>yy</i> argument is omitted when setting the system
    329 date and time.</p>
    330 <p>IEEE&nbsp;Std&nbsp;1003.1-2001/Cor&nbsp;1-2002, item XCU/TC1/D6/19 is applied, correcting the CHANGE HISTORY section.</p>
    331 </blockquote>
    332 <h4 class="mansect"><a name="tag_20_30_24" id="tag_20_30_24"></a>Issue 8</h4>
    333 <blockquote>
    334 <p>Austin Group Defect 466 is applied, replacing the list of conversion specifications for the +<i>format</i> operand with a
    335 requirement that the output is formatted as if by a call to <a href="../functions/strftime.html"><i>strftime</i>()</a> with
    336 specific arguments.</p>
    337 <p>Austin Group Defect 1122 is applied, changing the description of <i>NLSPATH .</i></p>
    338 <p>Austin Group Defect 1345 is applied, adding paragraphs to APPLICATION USAGE and RATIONALE about the default <i>date</i> utility
    339 format.</p>
    340 </blockquote>
    341 <div class="box"><em>End of informative text.</em></div>
    342 <hr>
    343 <p>&nbsp;</p>
    344 <a href="#top"><span class="topOfPage">return to top of page</span></a><br>
    345 <hr size="2" noshade>
    346 <center><font size="2">UNIX® is a registered Trademark of The Open Group.<br>
    347 POSIX™ is a Trademark of The IEEE.<br>
    348 Copyright © 2001-2024 The IEEE and The Open Group, All Rights Reserved<br>
    349 [ <a href="../mindex.html">Main Index</a> | <a href="../basedefs/contents.html">XBD</a> | <a href=
    350 "../functions/contents.html">XSH</a> | <a href="../utilities/contents.html">XCU</a> | <a href="../xrat/contents.html">XRAT</a>
    351 ]</font></center>
    352 <hr size="2" noshade>
    353 <div class="NAVHEADER">
    354 <table summary="Header navigation table" class="nav" width="100%" border="0" cellpadding="0" cellspacing="0">
    355 <tr class="nav">
    356 <td class="nav" width="15%" align="left" valign="bottom"><a href="../utilities/cxref.html" accesskey="P">&lt;&lt;&lt;
    357 Previous</a></td>
    358 <td class="nav" width="70%" align="center" valign="bottom"><a href="contents.html">Home</a></td>
    359 <td class="nav" width="15%" align="right" valign="bottom"><a href="../utilities/dd.html" accesskey="N">Next &gt;&gt;&gt;</a></td>
    360 </tr>
    361 </table>
    362 <hr align="left" width="100%"></div>
    363 </body>
    364 </html>