Guy Harris said:
Maybe this is *another* case where "some applications "misuse" tzdb identifiers" and where it might "be better to solve this on a more general level such as geo-location<=>timezone mappings", e.g. a meeting date shouldn't be tagged with {date/time, tzdb identifier} but with {date/time, geographic coordinates}. I'm not sure whether the geographic coordinates of the meeting location are more or less likely to change than the time zone rules of that location,
That doesn't always solve the problem; it can make it worse. For example, I have a meeting which *I* take part in at my location, but is booked for 07:00 Seattle time, not 15:00 UK time. I don't want it tagged with my location. -- Clive D.W. Feather | If you lie to the compiler, Email: clive@davros.org | it will get its revenge. Web: http://www.davros.org | - Henry Spencer Mobile: +44 7973 377646