🚀 go-pugleaf

In news.software.b, article <1991May28.151328.21097@zoo.toronto.edu>,
  henry@zoo.toronto.edu (Henry Spencer) writes:
< In article <5JL4MZ3@taronga.hackercorp.com> peter@taronga.hackercorp.com (Peter da Silva) writes:
< >You know, if it were just to treat undecipherable timezones as GMT that'd
< >pretty much solve the problem.
< 
< If I'm not mistaken, that's exactly what it does.  There is so much chaos
< in timezone abbreviations that just ignoring unknown ones is the only safe
< thing to do.  Note, however, that it must be a *timezone abbreviation* for
< it to be ignored.  Inscrutable garbage, e.g. an attempt to use an RFC822
< comment in RFC1036 where it is not legal, is a different story.

<6313530@mkist.ruhr.sub.org> unparsable Date: `10 Jun 91 18:60:58 MEST'
<A0b6tnji@hiss.han.de> unparsable Date: `Mon, 10 Jun 1991 22:26:08 MET DST'
<A0b6tph2@hiss.han.de> unparsable Date: `Mon, 10 Jun 1991 23:07:52 MET DST'

According to Henry, shouldn't at least the first of these be acceptable?

I don't know if " DST" is standard or not, but it's present in numerous
/etc/zoneinfo/* files. Ditto four-letter timezones.

-- 
Matthias Urlichs -- urlichs@smurf.sub.org -- urlichs@smurf.ira.uka.de     /(o\
Humboldtstrasse 7 - 7500 Karlsruhe 1 - FRG -- +49-721-621127(0700-2330)   \o)/