From: Neil Jerram <neiljerram@gmail.com>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Two problems with export to Google calendar
Date: Wed, 7 Dec 2022 11:52:45 +0000 [thread overview]
Message-ID: <CAKuG=vsdxRju3RHLt3hi+MpCdNX86EgYigmC7C1dGae0HLnxYQ@mail.gmail.com> (raw)
In-Reply-To: <CAKuG=vti=_1ZSe_AQh_OfrPf7YpBy+U2uUhXc--4GjBUxt=PKA@mail.gmail.com>
On Wed, 7 Dec 2022 at 11:30, Neil Jerram <neiljerram@gmail.com> wrote:
>
> Firstly, when I last exported during late summer, org generated an
> .ics file with
>
> X-WR-TIMEZONE:BST
>
> which I think was intended to mean British Summer Time; but Google
> interpreted it as Bangladesh Standard Time. As a result, my events
> from Org are shown at the wrong time in Google calendar.
>
> Secondly, it seems to me that the concept of having a timezone for the
> whole .ics file might be wrong. My Org files have dated events in
> both the summer and the winter, and it is obvious to me that the times
> for the summer events should be understood as British Summer time
> (UTC+1), and that the times for the winter events should be understood
> as GMT (UTC).
>
> Do others agree with that? If so, it would need to be reflected on
> export by each event having its own timezone, instead of a global
> timezone for the whole file.
>
> Best wishes,
> Neil
Ah, it looks like the solution for both points might be customizing
org-icalendar-timezone as "Europe/London". I will try that...
Neil
next prev parent reply other threads:[~2022-12-07 11:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 11:30 Two problems with export to Google calendar Neil Jerram
2022-12-07 11:52 ` Neil Jerram [this message]
2022-12-07 12:56 ` Ihor Radchenko
2022-12-07 14:00 ` Max Nikulin
2022-12-12 14:00 ` Ihor Radchenko
2022-12-12 16:53 ` Max Nikulin
2022-12-13 9:56 ` Ihor Radchenko
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKuG=vsdxRju3RHLt3hi+MpCdNX86EgYigmC7C1dGae0HLnxYQ@mail.gmail.com' \
--to=neiljerram@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).