Tom Gillespie <tgb...@gmail.com> writes: >> So I guess the timestamp format and the code which manages them will >> need the ability to use the full TZ name and not just the abbreviated >> form (and I guess an option to allow the user to select). In fact, we >> probably need a way to select between abbreviated/full dynamically as >> well as you might use the different TZ types as a way to flag which >> timestamps you want to adjust due to TZ changes (either in TZ db or in >> user location) and those you don't want changed. > > I think the only sane way to do this is to require timezone abbreviations > /expansions to be defined in the file itself and never in an init.el there is > simply too much ambiguity and if the information is lost we are out of luck.
I strongly disagree. I'd prefer to allow only internationally recognized time zone format. Let's not make life harder for Org file parsers. -- 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>
