wwp@yahoogroups.com:
Re: Editing extended - another 20 hours!
Bjørn K Nilssen 2008-Dec-31 09:23:00
On 30 Dec 2008 at 13:29, Landis wrote:
> >On 30 Dec 2008 at 11:45, Yahoo Account wrote:
> >
> >> first: sorry for any confusion the timeframe might have caused.
> >
> >Just a little tip: I'm sure there would be less confusion about
> >timeframes etc if you switched to the more commonly used global time
> >zone GMT (or UTC) instead of PST? I guess we all know where we are
> >in relation to GMT? Not so with the PST I'm afraid (although I can
> >read in the mail headers that it is -0800) After all this is
> >supposed to be a global geopanographic event, and then it feels a
> >bit strange to give the time in local Berkely time?
>
>
>
> Well, that's not too difficult for me. I usually just add the link
> to timeanddate.com so that everyone can be told in their own time
> zone, but if the rest of the world is pretty good about UTC, it's no
> problem for me.
>
> The server will lock at 1600 UTC on 31 December - http://tinyurl.com/9pl4cp
Thanks :)
I've always wondered why the time zone abbreviations are so badly organized that they
can't really easily be used for direct conversions. For instance the code CST can mean
either 'Central Summer Time' or 'Central Standard Time'. The first CST is UTC+10.30
(Australia), and the second CST can be either UTC+9.30 (Australia too!) or UTC-0600
(N.America). To make this even worse each time zone can also have several different
abbreviations, like PST=HNP=U=AKDT=HAY=UTC-0800.
--
Bj?rn K Nilssen - http://bknilssen.no - panoramas and 3D