Anthony Ball wrote: >I never had any luck finding anything to give me the future DST changes for >a timezone
We don't have an API for that. We've discussed it a bit, and will most likely add such a thing to the DT:TZ API after we've switched to the reimplemented DT:TZ, scheduled for 2012-09-01. > Now however the second >change in 2012 is coming up one second short, Smells like a leap second issue. There's a leap second scheduled for 2012-06-30T23:59:60Z. -zefram
