diff options
author | Paul Eggert <eggert@cs.ucla.edu> | 2022-05-17 15:47:35 -0700 |
---|---|---|
committer | Paul Eggert <eggert@cs.ucla.edu> | 2022-05-17 15:48:11 -0700 |
commit | 9cde39f881204e422d4bdad67ab12877d6a8172d (patch) | |
tree | 8fb210eea0f5a3b1408140f9a8faee363ffc7284 /doc/parse-datetime.texi | |
parent | 2e13b549ba1ef89f34533b03e3ad1799a7e9c287 (diff) | |
download | gnulib-9cde39f881204e422d4bdad67ab12877d6a8172d.tar.gz |
parse-datetime: support 'J' military time zone
Requested by Brian Inglis in:
https://savannah.gnu.org/support/?110644
* lib/parse-datetime.y (parser_control): New member J_zones_seen.
(item): New item 'J'.
(military_table): Add 'J'.
(parse_datetime_body): Set and use J_zones_seen.
* tests/test-parse-datetime.c (main): Test "J".
Diffstat (limited to 'doc/parse-datetime.texi')
-rw-r--r-- | doc/parse-datetime.texi | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/parse-datetime.texi b/doc/parse-datetime.texi index 575b4d5aea..44305d136c 100644 --- a/doc/parse-datetime.texi +++ b/doc/parse-datetime.texi @@ -304,7 +304,7 @@ Time zone items other than @samp{UTC} and @samp{Z} are obsolescent and are not recommended, because they are ambiguous; for example, @samp{EST} has a different meaning in Australia than in the United States, and @samp{A} has different -meaning as a military time zone than as an obsolescent +meaning as a military time zone than as an obsolete RFC 822 time zone. Instead, it's better to use unambiguous numeric time zone corrections like @samp{-0500}, as described in the previous section. |