DOT issues final ruling on Indiana time zones

Paul Schauble Paul.Schauble at ticketmaster.com
Thu Jan 19 21:57:25 UTC 2006


Probably I'm missing something, but why "2:00 AM CST to 1:00 AM CDT". In the
spring, 1:59:59 is followed 1 second later by 3:00:00 CDT. I don't
understand why you have it  in the other direction.

    ++PLS 

-----Original Message-----
From: tz-request at elsie.nci.nih.gov [mailto:tz-request at elsie.nci.nih.gov] On
Behalf Of Deborah Goldsmith
Sent: Wednesday, January 18, 2006 7:12 PM
To: tz at lecserver.nci.nih.gov
Subject: Re: DOT issues final ruling on Indiana time zones

You're right, that should have been "fall back from 2:00 AM EST to 1:00 AM
CST, then again from 2:00 AM CST to 1:00 AM CDT". Sorry about that.

 From the final DOT ruling (posted earlier) it appears as though that is in
fact the correct behavior, too, as odd as it is.

Deborah

On Jan 18, 2006, at 5:38 PM, Paul Schauble wrote:

> Since this is in the spring, shouldn't that last change be from 2AM 
> CST to 3AM CDT?
>
>     ++PLS
>
> -----Original Message-----
> From: tz-request at elsie.nci.nih.gov [mailto:tz- 
> request at elsie.nci.nih.gov] On Behalf Of Deborah Goldsmith
> Sent: Wednesday, January 18, 2006 5:38 PM
> To: tz at lecserver.nci.nih.gov
> Subject: DOT issues final ruling on Indiana time zones
>
> <snip>
> assuming I'm interpreting everything correctly. The DOT doesn't 
> specify whether Starke county switch to Central Time at the 
> appropriate time for its old or new time zone, but I'm assuming the 
> old here. That leads to it falling back from 2:00AM EST to 1:00AM CST, 
> and then again from 2:00AM CST to 1:00AM CST. If that makes people 
> nervous, then the transition would need to be at 3:00 AM.
>
> Deborah Goldsmith
> Internationalization, Unicode liaison
> Apple Computer, Inc.
> goldsmit at apple.com
>



More information about the tz mailing list