Eric Fischer said:
We just ran into a bug at work where users in US Central Time were identified as being in America/Indiana/Knox instead of in America/Chicago because code was running through the list of time zones in zone.tab looking for the first one that matched the current GMT offset and DST state, and America/Indiana/Knox is currently observing CDT and ordered before America/Chicago.
I hope this is actually a use that the file ordering is intended to support,
I don't see how it can be. In general, there are going to be multiple zones that match a given GMT offset and DST state, so what makes anyone think that the first one that matches is theirs? If it were always true, we wouldn't need the other ones. -- Clive D.W. Feather | Work: <clive@demon.net> | Tel: +44 20 8495 6138 Internet Expert | Home: <clive@davros.org> | Fax: +44 870 051 9937 Demon Internet | WWW: http://www.davros.org | Mobile: +44 7973 377646 THUS - a Cable and Wireless business