Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!tut.cis.ohio-state.edu!ucsd!helios.ee.lbl.gov!pasteur!jwz@teak.berkeley.edu
From: jwz@teak.berkeley.edu (Jamie Zawinski)
Newsgroups: comp.sys.ti.explorer
Subject: Re: that dang clock
Message-ID: <22190@pasteur.Berkeley.EDU>
Date: 16 Feb 90 21:04:27 GMT
Sender: news@pasteur.Berkeley.EDU
Lines: 12
In-reply-to: <9002161630.AA08943@ti.com>

Another "gotcha" to watch out for is the :TIMEZONE attribute of the namespace;
this can have some evil interactions with daylight savings time.  We used to
have this set to the string "PST" (Pacific Standard Time).  So what happened
was, the time parser took this string, realized that it was daylight savings
time, and turned it in to "PDT" (Pacific Daylight Time).  So then when the
conversion from TZ-string to TZ-number came, we got bumped to an earlier time
zone (MST and PDT are the same at some level of abstraction...)

I'm still not all that clear on where (or exactly what) the problem was, but
it went away when we changed :TIMEZONE to be 8 instead of "PST".

		-- Jamie