Tim Cross <[email protected]> writes: >> This is not the problem we need to worry about. We can use whatever >> Emacs provides and rely on future improvements in Emacs where things are >> deficient. We should not aim for 100% accurate time zone support. Just >> good enough. It's not Org's job to implement the gory details of time >> zone support. > > I guess we will have to disagree here. If org is going to claim to > support time zones, then 100% accurate is IMO essential. As it stands > now, we don't claim TZ support and time calculations are correct on the > basis they are all done relative to current locale. However, once you > add TZ information, if you don't apply it consistently and correctly, > that means the values can no longer be relied upon. > > Or to put it in another way - currently, it is well understood where org > timestamps fall down. However, once you add TZ and provide the > expectation TZ data will be respected correctly, all bets are off.
I think I need to clarify. Emacs currently relies on glibc time zone support on Linux. I am not sure if glibc is 100% accurate, but it should be good enough. At least, there is no way we can do better ourselves. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
