David T. Lewis wrote
> On Sat, Jan 12, 2013 at 09:02:49AM -0800, glenpaling wrote:
>> David T. Lewis wrote
>> > ...I put that in quotes because it turns out that the Squeak definition
>> of
>> > Smalltalk epoch is just plain wrong. It should be this:
>> > 
>> >   DateAndTime epoch ==> 1901-01-01T00:00:00-00:00
>> > 
>> > Not this:
>> > 
>> >   DateAndTime epoch ==> 1901-01-01T00:00:00-05:00
>> > 
>> > ...
>> 
>> I'm in the same timezone but when I tried DateAndTime epoch, I got
>> 1901-01-01T00:00:00+01:00. The general preference "use locale" isn't
>> enabled
>> in the 4.4 image (I'll add this to the 4.5 list). Timezone is stuck in
>> Frank's locale. Tim is this causing some of your problems? 
>> 
> 
> I also get an incorrect time zone offset if I use a fresh image:
> 
>   DateAndTime localTimeZone ==> a TimeZone(LT)
> 
>   DateAndTime localTimeZone offset ==> 0:01:00:00
> 
>   DateAndTime epoch ==> 1901-01-01T00:00:00+01:00
> 
> I didn't notice, as I normally have TimeZoneDatabase installed:
> 
>   DateAndTime localTimeZone ==> a TimeZoneProxy for America/Detroit (LMT)
> 
>   DateAndTime localTimeZone offset ==> -0:05:00:00
> 
> So perhaps there is a bug in initialization at image startup (but either
> way the DateAndTime epoch is wrong).
> 
> Dave

Not a bug, I just enabled useLocale in the preferences browser and restarted
the image. Timezone initializes correctly after that.

I agree, the epoch is wrong. What would be the consequences of setting it to
offset zero? 



--
View this message in context: http://forum.world.st/Locale-TimeZones-in-4-0-image-tp4663041p4663144.html
Sent from the Squeak - Dev mailing list archive at Nabble.com.