hi, Shiro, > With this, say the user have > > #+TIMEZONE: America/Toronto > > at the start of their org file, and they moved to Shanghai, all the timestamp > in > the org file is converted using something equivalent to > > $ TZ=Asia/Shanghai date --date='TZ="America/Toronto" '"$TIMESTAMP" > > and the file header changed to > > #+TIMEZONE: Asia/Shanghai > > when they get back the timestamp is returned with > $ TZ=America/Toronto date --date='TZ="Asia/Shanghai" '"$TIMESTAMP"
i can imagine buffer-wide time zone settings, especially if one has multiple .org files, could become hard to manage. i don't know the issues with evolving towards a syntax where time zone information is embedded in time stamps themselves, but i wonder if that might be more manageable. i *can* imagine that if needed, one might do one's own hack, such as your suggestion, while that evolution progresses. in particular, issues about entering, and displaying, time stamps, which need to be solved in either case, could then be tackled. i would think. cheers, Greg
