--- Begin Message ---
|
Subject: |
[bugs #11290] "date" cannot parse its own ISO 8601 output |
|
Date: |
Fri, 10 Dec 2004 07:38:43 -0500 |
This mail is an automated notification from the bugs tracker
of the project: GNU Core Utilities.
/**************************************************************************/
[bugs #11290] Full Item Snapshot:
URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=11290>
Project: GNU Core Utilities
Submitted by: 0
On: Fri 12/10/2004 at 07:38
Category: None
Severity: 5 - Average
Item Group: None
Resolution: None
Privacy: Public
Assigned to: None
Status: Open
Summary: "date" cannot parse its own ISO 8601 output
Original Submission: As shown in (1) below, date can produce valid ISO 8601
output. However, as shown in (2), it cannot parse that output. Even worse, as
shown in (3), once the time zone information is removed, date interprets the
"T" separator as a non-standard, undocumented and incompatible time zone
specification. The "T" has to be replaced by a space before the output can be
parsed acceptably, as shown in (4). So, the current behavior of date hinders
the usage of ISO 8601 formatted dates in configuration and state text files.
(0)$ date --version
date (coreutils) 5.2.1
(1)$ date -Iseconds
2004-12-10T13:27:59+0100
(2)$ date -d "2004-12-10T13:27:59+0100"
date: invalid date `2004-12-10T13:27:59+0100'
(3)$ date -d "2004-12-10T13:27:59"
Fri Dec 10 07:27:59 CET 2004
(4)$ date -d "2004-12-10 13:27:59"
Fri Dec 10 13:27:59 CET 2004
For detailed info, follow this link:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=11290>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
--- End Message ---