Brendon Oliver wrote:
On Tuesday 20 February 2007 11:04, Jeff Garland wrote:
Sorry, nobody has gone and done it in anger yet...guess it's getting to be almost an emergency now. It's been in my work queue for awhile now -- it pretty much has to get done this week. Anyway, if you take a shot at it and send it to me I can check and test against it -- that would be a help. I've promised to try and get it in 1.34, but we will clearly need a version for folks using 1.33 posted in the vault or somewhere.
I thought as much. I'm currently cobbling together a perl script to check all the america/* records from the csv file against the system zoneinfo files & updating the records accordingly. I'll post a copy when I'm done for you to check.
OTOH, if anyone can think of a better way to figure out which zone records need updating, I'd be glad to hear it. FWIW, I'm in Australia and not really familiar with the US timezones (which is why I decided to use the zoneinfo files as the 'authoritative' source), but our application needs to be aware of the DST change.
Thanks to a helping hand by Brendon I've made and update to the 1.34 release candidate and the CVS head with the new timezone rules for US/Canada (Mexico isn't changing). This file will also work with 1.33.x, so you don't need to update your whole install just for the new time zone data. I've uploaded it to the vault/date-time section here: http://boost-consulting.com/vault/index.php?&direction=0&order=&directory=date_time I'd appreciate if someone from Indiana could look over the rules for that state...not really sure those are 100% yet. One last note on the use of this file. As has been discussed previously on this list, the library will only give correct answers for current/future date conversions now that the rules have changed. So if you are converting dates from earlier years the answers will reflect current time zone rules not past rules. The library doesn't support historic timezone rules presently. Thx again to Brendon for the assist! Jeff