From mboxrd@z Thu Jan 1 00:00:00 1970 From: Philipp Haselwarter Subject: Re: Status google calendar sync Date: Sat, 11 Jun 2011 15:25:00 +0200 Message-ID: <874o3wa4b7.fsf@nzebook.haselwarter.org> References: <8762t3idd3.fsf@gmx.ch> <4D48E887.20900@gmail.com> <5E7BEB01-1411-4BF4-A36B-C4FF43E55CF6@fastmail.net> <6843D3C6-E3B7-4D31-9F4C-163FA3770D71@fastmail.net> <4DF24E8E.5010200@lbl.gov> <4DF26BD0.4000001@lbl.gov> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:45568) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QVOBh-00074C-O8 for emacs-orgmode@gnu.org; Sat, 11 Jun 2011 09:25:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QVOBg-0007nc-Mc for emacs-orgmode@gnu.org; Sat, 11 Jun 2011 09:25:17 -0400 Received: from lo.gmane.org ([80.91.229.12]:59388) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QVOBg-0007nI-D5 for emacs-orgmode@gnu.org; Sat, 11 Jun 2011 09:25:16 -0400 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QVOBf-0008FE-6d for emacs-orgmode@gnu.org; Sat, 11 Jun 2011 15:25:15 +0200 Received: from 187.93.114.78.rev.sfr.net ([78.114.93.187]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 11 Jun 2011 15:25:15 +0200 Received: from philipp.haselwarter by 187.93.114.78.rev.sfr.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 11 Jun 2011 15:25:15 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Unfortunately, both the awk script and the org-export-icalendar seem to have quite a hard time with repeating entries. ical2org does not honor RRULE at all, the export has some very basic and very fragile support, but anything like <%%(org-diary-class 16 02 2011 18 05 2011 3)> or SCHEDULED: <2011-02-20 Sun +1w -2d> already fails it. I think this is an important topic, especially wrt mobile devices. Better interoperability with other calendering systems would greatly benefit the org user experience. -- Philipp Haselwarter