Commit Graph

10 Commits

Author SHA1 Message Date
aj
63c8a29198 updated the readme. error-tested the local_to_utc methods. light changes to the makefile 2010-11-14 01:38:23 -08:00
aj
c795abf2b6 misspelled "Olson". sorry 'bout that, Art. 2010-11-07 13:00:21 -08:00
aj
329f699e51 alerted to buginess in README. added notes & zic reference. removed local_to_utc conversion for now.
Time comparisons are patently wrong. They do not consider s/w/u/g/z time modifiers, so the comparisons can be off by hours. At least 24 hours within any time or zone change, ezic will give unreliable results.
I think a solution can involve "flattening" the data, starting from the earliest time possible for each zone/rule, going forward.
There exist ambiguous local times for zones and rules. For example, on Nov 7th, in Los Angeles, the times from 1:00:00am to 1:59:59am were repeated, once for PDT and once for PST. Given a local time in that zone between those times, we cannot determine what UTC time is unambiguously. Similar for Zone transitions where fall-back occurs.
2010-11-07 12:52:51 -08:00
aj
4d95017b7f made License terms more explicit 2010-11-07 00:56:23 -07:00
aj
2e424038a2 README smithing. License update 2010-11-04 22:15:49 -07:00
aj
9178a6c148 README smithing 2010-11-04 22:02:13 -07:00
aj
d5cb707119 renamed the API methods, updated the README 2010-11-04 21:31:29 -07:00
aj
298b245668 updated readme 2010-11-04 05:14:06 -07:00
aj
b967cd3ff7 fleshed out tzdata records, and internal format. also, licence=PUBLIC DOMAIN! 2010-11-03 00:49:30 -07:00
aj
992a7d8e1a the seed of an (likely bad) idea. 2010-11-03 00:22:58 -07:00