Re: Timezone/Encoding issues when exporting as ics and importing to Google Calendar

[Nick Dokos <nicholas.dokos@hp.com>]

Tassilo Horn <tassilo@member.fsf.org> wrote:

> Hi all,
> 
> I export all my org-files as icalendar files, push them to some
> webserver from which google calendar imports them.  Basically, that
> works pretty good except for two things:
> 
> 1. Encoding: All Umlauts and other non-ASCII chars show up as boxes in
>    google calendar.  When visiting some exported ics file and doing M-x
>    describe-coding-system, I get utf-8-unix for those files.  Doesn't
>    google calendar support UTF-8?  And if so, is there a way to export
>    as latin1 if that is supported by google?
> 
> 2. Timezone: I live in Germany and thus all my timestamps are CEST.  The
>    exported ics file properly declare X-WR-TIMEZONE:CEST.  However,
>    since we also have DST, in summer all appointments show up 2 hours
>    late, and in winter my appointments show up 1 hour late.  Is there
>    anything I can do about it?  The google calendar settings have CEST
>    as timezone...
> 

I don't know if this is the problem you are running into, but 
icalendar--convert-tz-offset is buggy as-is: it looks as if
additional work was planned for it, but it never got done.
In particular, it assumes there is an RRULE in the icalendar file
and does not translate timezones otherwise.

Reading your mail again, I guess you are having problems in the
other direction, but IME, if there is a bug somewhere, there is
at least one more going the other way :-) 

Nick