Re: a human-eye date format everyone can love

On Mon, Jun 24, 2002 at 02:11:57PM -0500, Karl Fogel wrote:
> Hontvari Jozsef <hontvari@solware.com> writes:
> > > There are timezones which are on a half-hour alignment, not
> > > whole-hour. (Australian central time, for example.)
> >
> > Yes, in those cases we have to use four digits. But use the shorter form
> > when possible.
>
> But isn't it important to be fixed-width, for the standards-compliant
> portion?

Agreed.

And personally, I find the -0500 to be much more legible. The -05 doesn't
look like a timezone to me. Heck, just look at what my mailer did with the
quoting of Karl's mail above.

Hmm. That raises a point. All the software that I've seen that deals with
timezones will always use 0-padded 4-digit values. While somebody could
certainly find something that shortens to two digits, I'll argue that it is
not "typical".

Let's keep the four digit timezones.

For the () part, I'd suggest the following form:

    (Mon, 24 Jun 2002)

i.e. separate the day name from the date; don't embed the comma within the
date portion

Note: the space before the timezone is illegal. According to section 5.3.4.2
of ISO 8601:2000(E), "... shall be appended to the representation of the
local time following immediately, with space, ..."

Thus, the format would be (with my suggestion for the paren part):

  2002-06-24 13:31:19-0700 (Mon, 24 Jun 2002)

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org