9 Nov
2012
9 Nov
'12
11:56 a.m.
On 2012-11-09 12:29, Jeff Garland wrote:
In bdt the time_zone is abstract -- so you can build your own time zone names and such in any fashion you like. What's needed to handle all the historic cases correctly is a derivative of time_zone which has the history and when asked to convert local to utc, adjusts appropriately for the relative time historically (effectively a list of offset rules).
Unfortunately, time_zone_base is not able to handle "any fashion you like", e.g., the Olsen database. It assumes exactly 2 switches per year, whereas there are cases that require 1 or 3 time zone changes in a single year. Cheers, Rutger