From: Tim Cross <firstname.lastname@example.org>
Subject: Re: org-table change time from UTC to other timezones
Date: Sun, 13 Dec 2020 09:52:26 +1100 [thread overview]
Message-ID: <email@example.com> (raw)
Maxim Nikulin <firstname.lastname@example.org> writes:
> 2020-12-12 Alan E. Davis wrote:
>> Thank for the clear explanation. My little problem seems to require a
>> super steam hammer. Your insights are most helpful.
> In my opinion, org mode is too rigid in respect to timestamp format.
> Sometimes I would prefer to specify timestamps with timezone.
> Well known example of idiosyncrasy of particular applications.
> Timestamps in xls files are represented by floating point numbers,
> namely days since 1 Jan 1900, fractional part is time. Unfortunately
> 1900 is not a leap year, so to avoid unnecessary complications of code
> and keep memory footprint small, on Macs epoch starts in 1904, on
> windows year 1900 has Feb, 29...
Although there are likely some dark corners where bugs can be found, I
think you could probably add timezone data to org timestamps by changing
the default format strings. Org also uses an 'internal' 'time' value to
represent timestamps which are then converted to the required format
using these format strings.
What is possibly missing is an easy way to specify a time zone when
creating a timestamp. I suspect it will default to whatever the local
system tz is and I don't think there is any convenient way to change tz
values like there is for the other timestamp components.
next prev parent reply other threads:[~2020-12-12 22:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 10:20 org-table change time from UTC to other timezones Alan E. Davis
2020-12-09 11:34 ` Tim Cross
2020-12-10 8:10 ` Alan E. Davis
2020-12-10 19:01 ` Tim Cross
2020-12-11 0:12 ` Alan E. Davis
2020-12-11 15:40 ` Maxim Nikulin
2020-12-11 22:44 ` Alan E. Davis
2020-12-12 16:04 ` Maxim Nikulin
2020-12-12 22:52 ` Tim Cross [this message]
2020-12-13 3:14 ` Alan E. Davis
2020-12-13 17:03 ` Maxim Nikulin
2020-12-14 2:29 ` Alan E. Davis
2020-12-12 3:31 ` Jean Louis
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).