🚀 go-pugleaf

Richard Stallman writes:
 > It seems to me that all the world's time zones should be equally valid,
 > and that the US is hardly entitled to expect the rest of the world
 > to obey a standard that allows only US time zone names.
 >  
 > I think elm and any other programs that can't handle any old timezone name
 > should be fixed to do so.

I don't know that it can be done.  There are name collisions that
can be dealt with only by guessing which time zone is really meant.

Timezone names are on their way out in Internet mail and good
riddance to them.  Programs that generate dates should use numeric
timezone specifications always and avoid the confusion with the
names.

RFC 1123, section 5.2.14

         There is a strong trend towards the use of numeric timezone
         indicators, and implementations SHOULD use numeric timezones
         instead of timezone names.  However, all implementations MUST
         accept either notation.  If timezone names are used, they MUST
         be exactly as defined in RFC-822.

         The military time zones are specified incorrectly in RFC-822:
         they count the wrong way from UT (the signs are reversed).  As
         a result, military time zones in RFC-822 headers carry no
         information.