stephen@dcl-cs.UUCP (Stephen J. Muir) (06/07/85)
Some news sites in the U.K. put the string "BST" in their date fields. This causes problems as the "getdate()" routine doesn't recognise "BST". The recommended fix, meanwhile, is to use "GMT". -- NAME: Stephen J. Muir Project:Alvey ECLIPSE Distribution JANET: stephen@uk.ac.lancs.comp DARPA: stephen%lancs.comp@ucl-cs UUCP: ...!ukc!icdoc!dcl-cs!stephen PHONE: +44 524 65201 Ext. 4599 POST: Department of Computing, University of Lancaster, Bailrigg, Lancaster. LA1 4YR
smb@ulysses.UUCP (Steven Bellovin) (06/08/85)
> In article <192@dcl-cs.UUCP> stephen@dcl-cs.UUCP (Stephen J. Muir) writes: > >Some news sites in the U.K. put the string "BST" in their date fields. > >This causes problems as the "getdate()" routine doesn't recognise "BST". > >The recommended fix, meanwhile, is to use "GMT". > On the contrary the recommended fix is the one posted by Cathy Garlic a while > back. Recommended here means it is the one I'll be using so it will be > on the same tape as the next UKUUCP release (Xmas time). > > Whilst in the area any news on 2.10.3 or even the semi-mythical 2.11? Getdate() was originally written to conform with RFC733, the then-current ARPAnet mail standard. It used "BST" as "Bering Standard Time". RFC822 dropped BST, but getdate() has never been fully upgraded. Although any fixes should be installed, the best solution for an international network is to use GMT; it's unambiguous, and makes it easy for a receiving site to display the date in local time.
lmcl@ukc.UUCP (L.M.McLoughlin) (06/14/85)
In article <192@dcl-cs.UUCP> stephen@dcl-cs.UUCP (Stephen J. Muir) writes: >Some news sites in the U.K. put the string "BST" in their date fields. >This causes problems as the "getdate()" routine doesn't recognise "BST". >The recommended fix, meanwhile, is to use "GMT". On the contrary the recommended fix is the one posted by Cathy Garlic a while back. Recommended here means it is the one I'll be using so it will be on the same tape as the next UKUUCP release (Xmas time). Whilst in the area any news on 2.10.3 or even the semi-mythical 2.11?