On 22/04/16 17:13, Random832 wrote:
On Fri, Apr 22, 2016, at 12:04, Matt Johnson wrote:
I don't really like the zone-now.tab idea, because it would just reflect things as of the date of the tzdata release, which is somewhat arbitrary with respect to the scenario. How is that different from the fact that literally everything else in the release reflects things as of the date of the release?
The point is that the zones that are "merged" are _obsolete_, and therefore no-one who newly selects their timezone after that date "should" be using them anymore if they don't need historical timestamps.
One of the complaints has been that there are too many sets of timezone rules, but combining several zones that NOW have the same set of rules misses the point that there IS a lot of historic material and looking back at even just as far as the 2nd world war requires subtle differences. It would seem that the historic changes in Russian locations are also now getting accurate amendments to the rules, and simply hiding that information in 'backzone' needs to be clearly displayed when people using calendars that have 'simplified things' by stripping anything prior to 1970. Something substantial to prevent users from being given any offsets when the data is not available. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk