On 14/01/2023 22:05, Ihor Radchenko wrote:
In addition, we may provide some mechanism to set the time zone for:
1. Individual files
2. For all files, including possible time zone transitions over time.
What I mean by (2) is when the user travels from, say, Australia to USA,
it could be possible to say: Use Australia/Seattle up to certain time
and then use USA/Austin.
I like this idea.
Having a time handling library supporting custom ad hoc timezones it
would be possible to create a special zone for such trip. Its time
offset and naming rules follows locations of the trip. As a result,
supplying various timezones to agenda generation code it would be
possible to generate schedule for
- the traveling user with time local to each trip point (custom TZ)
- colleagues and relatives staying at the departure point (original TZ)
- accepting party (destination TZ)
For a timestamp without explicit timezone it may be obtained from
- subtree or file property (single value or list of time intervals
reflecting history of timezone changes)
- buffer local variable (single TZ or history)
- global org variable (single TZ or history)
- timezone (single value) set inside libc (e.g. initialized from the TZ
environment or changed by code)
- system timezone.
