> Date: Fri, 11 Dec 2009 18:12:03 -0800 (PST)
> From: Ienup Sung <is at sac.sfbay.sun.com>
> Subject: Date/time conversion specification compatibility
> [PSARC/2009/677 FastTrack timeout 12/18/2009]
Hi Ienup,
I support the changes in functionality provided by this case.
However, I have a few minor quibbles with the references to ISO 8601
in the provided man page updates:
1. A revision to ISO 8601 was adopted in 2004, so ISO 8601:2000 is
obsolete.
2. ISO 8601 specifies dozens of "standard date formats" so saying that
%F uses "the ISO 8601:2000 standard date format" is misleading.
3. It is strange that %F specifies an ISO 8601 Extended format (with '-'
separators between fields) and a %z using Basic format (without a ':'
separator). ISO 8601 explicitly disallows any date and time
representation where basic and extended formats are mixed; all date,
time, and offset fields must be in basic format, or all of the
fields must be in extended format.
>From getdate(3c):
%F Equivalent to %Y-%m-%d (the ISO 8601:2000 standard date |
format). |
should be:
%F Equivalent to %Y-%m-%d (the ISO 8601:2004 standard date |
in extended format). |
and:
%z Offset from UTC in ISO 8601:2000 standard format (+hhmm |
or -hhmm), or no characters if no time zone is determinable. |
should be:
%z Offset from UTC in ISO 8601:2004 standard basic format (+hhmm |
or -hhmm), or no characters if no time zone is determinable. |
The same changes are needed to the %F and %z descriptions in strftime(3c)
and strptime(3c).
Cheers,
Don
