Lester Caine <lester@lsces.co.uk> wrote on Thu, 29 Oct 2015 at 00:17:50 +0000 in <563165AE.7000404@lsces.co.uk>:
SIMPLE things like that are not the problem. Where the problem arises is when the 9:00AM UTC Meeting in one location is advertised in several time zones and one of those time zones has a change of offset.
Again, this is a user interface problem. A 0900 UTC meeting is advertised as 0900 UTC, period. Clients convert to local time if appropriate. What is the problem that the tzdb should be addressing here? I do not see it.
But my other problem is with the local tz identifiers which have different values in backzone pre-1970. In particular the UK zones which
Again, it is extremely difficult to parse your speech here, but we do not really address pre-1970 issues. I think it is out of the tz project's scope. --jhawk@mit.edu John Hawkinson
I have historic data that was UTC normalized for the second world war period, but gets miss displayed if backzone offsets are omitted. Some European id's have a similar problem. The original data from some 20 years ago was normalized using older versions of TZ, but the chronology did not work and when investigated, the missing elements of TZ data were identified, but have now been flushed to backzone ... how can it be ensured that the correct local times are displayed rather than the incorrect ones provided by a non-backzone TZ?