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

Hi Kevin, Kevin Brubeck Unhammer unham...@fsfe.org writes: I guess I'll have to upgrade my org-mode version (6.33x) to get org-icalendar-date-time-format? Not sure this will fix your problem, but yes, 6.33x is kinda prehistoric now. Best, -- Bastien

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

Bastien b...@gnu.org writes: Hi Kevin, Kevin Brubeck Unhammer unham...@fsfe.org writes: I guess I'll have to upgrade my org-mode version (6.33x) to get org-icalendar-date-time-format? Not sure this will fix your problem, but yes, 6.33x is kinda prehistoric now. Best, I ended up

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

Tassilo Horn tass...@member.fsf.org writes: Nick Dokos nicholas.do...@hp.com writes: Hi Nick, 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

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

Tassilo Horn tass...@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

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

Nick Dokos nicholas.do...@hp.com writes: Hi Nick, 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