cathy@ru-cs44.UUCP (Cathy Garlick) (08/09/83)
This article arrived here on Friday 5th August, but claims to have
been posted on Wed. 10th August, it's only 8th Aug. today! Something
somewhere is obviously up the spout. I reckon it's something to do
with timezones and us having different meanings for different
abbreviations. For instance, BST, in getdate.y BST seems to refer to
some timezone down the Bering Straits or something 11 hours different
from GMT instead of British Summer Time 1 hour different. My theory is
that the original article was posted on the afternoon of Wed. 3rd Aug.
somewhere in between 11 hours or so was added to the time making it
Thursday morning (4th), however it still had Wed. on it so it took the
next available Wednesday ie Wed. 10th Aug. It might sound a bit wierd
but has anyone any other suggestions?
Cathy Garlick {vax135,mcvax}!ukc!ru-cs44!cathysmb@ulysses.UUCP (08/10/83)
Cathy Garlick's diagnosis appears to be correct. Giving getdate a string containing a date and a day-name means "find the first occurrence of that day-name on or after the given date". Thus, if there's a timezone problem, the date portion could easily yield the next day, in which case specifying a day-name could move the date even further off. The root problem is indeed that BST was called "Bering Standard Time"; the list of timezone names was taken from RFC733, which had never heard of British Summer Time. It should be an easy fix.... --Steve Bellovin
Lauren Weinstein <lauren@vortex.UUCP> (08/10/83)
I just checked, and the dates on all of my recent articles have been correct as sent. If dates are being mangled, it must be somewhere upstream... If anybody finds out what's going on in this regard, please let us all know! Thanks. --Lauren--
ecn-ec:ecn-pc:ecn-ed:vu@pur-ee.UUCP (08/10/83)
See net.space #1844: I read it yesterday (Aug 9) but the date on it was Aug 14 !