Bug#434962: International date format is not ISO 8601 compliant.
On Wed, Jan 02, 2008 at 11:19:42PM +0100, Toni Mueller wrote: I'll talk to upstream about it, but personally think that while you are formally correct, legibility is actually increased by using a dot. Today I ran into a specific use case where the current behaviour is clearly detrimental. To wit: GNU date's -d switch doesn't understand a period separator. $ date -R -d 2008-07-05.09:17:19 date: invalid date `2008-07-05.09:17:19' $ date -R -d 2008-07-05T09:17:19 Sat, 05 Jul 2008 12:17:19 +1000 This wasted time when I was trying to RFC 2822ify dates from Darcs' roundup instance, prior to injecting them (along with other data) into a mail system. Perhaps upstream would prefer to adopt RFC 3339 rather than ISO 8601? It's a significantly simpler standard, and appears to use whitespace rather than a period or a T (which personally I think is the most readable of the three). $ date --rfc-3339 seconds -d 2008-07-05T09:17:19 2008-07-05 12:17:19+10:00 GNU date's -d switch also understands RFC 3339 format: $ date -Iseconds -d '2008-07-05 12:17:19' 2008-07-05T12:17:19+1000 PS: I also notice that the timezone information is missing. If the BTS is accessible internationally (as is the case for bugs.darcs.net), this can result in the timestamp being wrong by a whole day! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#434962: International date format is not ISO 8601 compliant.
Hello Trent, On Sat, 28.07.2007 at 10:42:00 +1000, Trent W. Buck [EMAIL PROTECTED] wrote: The _User Guide_ document states that | Date-and-time stamps are specified with the date in international | standard format (-mm-dd) joined to the time (hh:mm:ss) by a | period .. AFAICT this is *not* the international standard format; both ISO 8601 and RFC 3339 seem to recommend if not mandate the uppercase roman letter T where Roundup expects a period. this is correct, but your reading of the user guide appears to be debatable from my point of view. If you re-read the quote you presented in your bug report, you may find that the wording is crafted to attribute the international date format only to the date, not the time. I agree that the explanation could be clearer to specifically note that the timestamp format used is not ISO compliant, though. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#434962: International date format is not ISO 8601 compliant.
Hi, I'll talk to upstream about it, but personally think that while you are formally correct, legibility is actually increased by using a dot. That notwithstanding, either the documentation or the program should be changed to remove the invalidity of the claim. Best, --Toni++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#434962: International date format is not ISO 8601 compliant.
Package: roundup Version: 1.3.3-3 Severity: wishlist The _User Guide_ document states that | Date-and-time stamps are specified with the date in international | standard format (-mm-dd) joined to the time (hh:mm:ss) by a | period .. AFAICT this is *not* the international standard format; both ISO 8601 and RFC 3339 seem to recommend if not mandate the uppercase roman letter T where Roundup expects a period. From http://en.wikipedia.org/wiki/ISO_8601: | Combined representations | | | dateTtime dateTtimeZ | | Combining date and time representations is quite simple. It is in | the format of dateTtime. The date and time sections are any | proper representation of the date and time created by following the | standard. A common use could be | []-[MM]-[DD]T[hh]:[mm]:[ss]±[hh]:[mm]. | 1981-04-05T14:30:30-05:00 or | [][MM][DD]T[hh][mm][ss]Z. 19810405T193030Z, for example. | | The date and time representations may sometimes appear in proximity, | separated by a space or other characters, in which case they occupy | two separate fields in a data system, rather than a single combined | representation. This is sometimes done for human readability. Unlike | the above example, 1981-04-05 14:30:30-05:00 are two separate | representations, one for date and the other for time. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.21-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages roundup depends on: ii adduser 3.104 add and remove users and groups ii python2.4.4-6An interactive high-level object-o ii python-central0.5.14 register and build utility for Pyt roundup recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
