🚀 go-pugleaf

In article <1990Dec15.180350.5920@alphalpha.com>, nazgul@alphalpha.com (Kee Hinckley) writes:
|> In article <keld.661207816@dkuugin> keld@login.dkuug.dk (Keld J|rn Simonsen) writes:
|> >Why don't we do like sendmail has done it for ages?
|> >Write "GMT+2" for somebody (like me and most of other western
|> >European people) being two hours ahead of GMT.
|> What do you do for places where the timezone bumps by less than
|> an hour (I hear Saudia Arabia does it in minutes).
For what it's worth, "GMT+2" doesn't meet the RFC 822 specification.
"+0200" does.  So does "+0032", if that's what you want.

Someone else said:
|>Here's my personal opinion for what it is worth.  I like the headers
|>that use the numeric offset with a description in parentheses, such as:
|>Date: 14 Jun 1990 11:23:35 -0800 (PDT) 
|>Another alternative which I have not seen but might be nice is:
|>Date: 14 Dec 1990 11:23:35 -0700 (Pacific Std Time)
I basically agree with this, but watch out for time zone names that contain
characters with the high bit on!  I don't know that any are in use, but
as far as I know, there's nothing in the (other) time zone mechanisms to
prevent them from being created.

-- 
Topher Eliot
Data General Corporation                eliot@dg-rtp.dg.com
62 T. W. Alexander Drive                {backbone}!mcnc!rti!dg-rtp!eliot
Research Triangle Park, NC 27709        (919) 248-6371
Obviously, I speak for myself, not for DG.