Mercurial > hg > octave-kai > gnulib-hg
changeset 16968:20011163d6c7
parse-datetime: doc tuneup
* doc/parse-datetime.texi: Index "leap seconds" and fix minor
spacing issues.
author | Paul Eggert <eggert@cs.ucla.edu> |
---|---|
date | Fri, 06 Jul 2012 00:43:22 +0000 |
parents | f3f8be3a527d |
children | b284d21804b8 |
files | ChangeLog doc/parse-datetime.texi |
diffstat | 2 files changed, 12 insertions(+), 3 deletions(-) [+] |
line wrap: on
line diff
--- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2012-07-05 Paul Eggert <eggert@cs.ucla.edu> + + parse-datetime: doc tuneup + * doc/parse-datetime.texi: Index "leap seconds" and fix minor + spacing issues. + 2012-07-05 Akim Demaille <akim@lrde.epita.fr> do-release-commit-and-tag: fix the previous commit
--- a/doc/parse-datetime.texi +++ b/doc/parse-datetime.texi @@ -117,10 +117,10 @@ The output of the @command{date} command is not always acceptable as a date string, not only because of the language problem, but also because there is no -standard meaning for time zone items like @samp{IST}. When using +standard meaning for time zone items like @samp{IST}@. When using @command{date} to generate a date string intended to be parsed later, specify a date format that is independent of language and that does not -use time zone items other than @samp{UTC} and @samp{Z}. Here are some +use time zone items other than @samp{UTC} and @samp{Z}@. Here are some ways to do this: @example @@ -145,6 +145,7 @@ nested. Hyphens not followed by a digit are currently ignored. Leading zeros on numbers are ignored. +@cindex leap seconds Invalid dates like @samp{2005-02-29} or times like @samp{24:00} are rejected. In the typical case of a host that does not support leap seconds, a time like @samp{23:59:60} is rejected even if it @@ -237,6 +238,7 @@ 20:02-0500 # In @sc{est} (U.S. Eastern Standard Time). @end example +@cindex leap seconds More generally, the time of day may be given as @samp{@var{hour}:@var{minute}:@var{second}}, where @var{hour} is a number between 0 and 23, @var{minute} is a number between 0 and @@ -497,6 +499,7 @@ of seconds with nanosecond subcounts, and can represent all the times in the known lifetime of the universe to a resolution of 1 nanosecond. +@cindex leap seconds On most hosts, these counts ignore the presence of leap seconds. For example, on most hosts @samp{@@915148799} represents 1998-12-31 23:59:59 @sc{utc}, @samp{@@915148800} represents 1999-01-01 00:00:00 @@ -585,4 +588,4 @@ @cindex Berry, K. This chapter was originally produced by Fran@,{c}ois Pinard (@email{pinard@@iro.umontreal.ca}) from the @file{parse_datetime.y} source code, -and then edited by K.@: Berry (@email{kb@@cs.umb.edu}). +and then edited by K. Berry (@email{kb@@cs.umb.edu}).