ambiguous, but I don't have an idea on what would
be better. Maybe people that have those can chime in.
Best,
Shironeko
pointers. Like how
would I go about finding all the timestamps and make changes. Perhaps somewhere
in org that does something similar.
Regards,
shironeko
signature.asc
Description: This is a digitally signed message part
The only ambiguous timestamp is the hour when exiting DST (dialing back), and
that time is usually set to when there is not much going on (like midnight). all
other time do not need to specify whether its DST or not, which fits in with the
current timestamp format.
signature.asc
Description:
tz database and tools using it like the date(1) command can convert between
local times taking into account all the difference like daylight savings time.
An example below, Toronto observes daylight savings whereas Shanghai does not:
$ TZ=Asia/Shanghai date --date='TZ="America/Toronto" 2021-11-07
see https://en.m.wikipedia.org/wiki/Tz_database
On Sat, 2021-04-03 at 10:37 +1100, Tim Cross wrote:
>
> 1. Timzone alone is not sufficient. Offsets from UTC change due to
> daylight savings times etc.
>
> 2. You can easily have timestamps from different timezones in the same
> org file
>
> 3. Storing timestamps in local time is problematic
On Fri, 2021-04-02 at 13:34 +0200, to...@tuxteam.de wrote:
> On Thu, Apr 01, 2021 at 07:40:47AM +0000, shironeko wrote:
>
> Hm. Just a mumbling from the peanut gallery: isn't the timezone a property
> of the timestamp itself?
>
> Specifying the timezone for the whol
compatible, and it should do the job well enough.
Regards,
shironeko
compatible, and it should do the job well enough.
Regards,
shironeko
