From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Spiers Subject: Re: .ics export violates RFC2445 Date: Tue, 27 May 2008 22:55:57 +0100 Message-ID: <20080527215557.GD20846@atlantic.linksys.moosehall> References: <20071107205621.GT13544@atlantic.linksys.moosehall> <2DE7990C-2666-430E-91F5-B34C4A35699D@science.uva.nl> <20080429141240.GA9068@atlantic.linksys.moosehall> <2989BE0D-4A88-4DEC-B6A2-66B08661942F@science.uva.nl> <20080429171635.GB9068@atlantic.linksys.moosehall> Reply-To: Adam Spiers Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K179I-00020R-HN for emacs-orgmode@gnu.org; Tue, 27 May 2008 17:56:04 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K179G-00020F-D6 for emacs-orgmode@gnu.org; Tue, 27 May 2008 17:56:03 -0400 Received: from [199.232.76.173] (port=40813 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K179G-00020C-9j for emacs-orgmode@gnu.org; Tue, 27 May 2008 17:56:02 -0400 Received: from mail.beimborn.com ([70.84.38.100]:37395) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1K179F-00015z-PE for emacs-orgmode@gnu.org; Tue, 27 May 2008 17:56:02 -0400 Received: from mail.beimborn.com (localhost.localdomain [127.0.0.1]) by mail.beimborn.com (8.12.11.20060308/8.12.8) with ESMTP id m4RLu0Y8029782 for ; Tue, 27 May 2008 16:56:00 -0500 Received: from localhost (localhost [[UNIX: localhost]]) by mail.beimborn.com (8.12.11.20060308/8.12.11/Submit) id m4RLu0L1029777 for emacs-orgmode@gnu.org; Tue, 27 May 2008 22:56:00 +0100 Content-Disposition: inline In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: org-mode mailing list On Thu, May 15, 2008 at 10:33:17AM +0200, Carsten Dominik wrote: > On Apr 29, 2008, at 7:16 PM, Adam Spiers wrote: > >>>Also, it would be great if a UID field could be generated for each > >>>event, perhaps by checksumming the contents of the event in some > >>>way. [snipped] > >>I guess we could create one, but this UID would then have to be > >>stored in the entry, as a property. Exporting to ical again must > >>then re- use the old uid each time. > >> > >>My org-id.el in the contrib directory allows already to create > >>unique identifiers, and it would be easy enough to include the > >>domain to make them truely unique, wordwide. > >> > >>However, right now I am hesitating to force a property drawer onto > >>every entry that ever is exported to iCalendar. But as an option, > >>this might really be good and eventually allow true > >>synchronization. > > > >I understand your hesitation - as an option that sounds perfect. > > Please get the latest GIT version of Org. Then set the variable > > (setq org-icalendar-force-UID t) > > and try to export to iCalendar. > > Right now, I am only forcing and using the ID for VEVENT. I am not > using it for VTODO, because I am not sure if it is allowed to have the > same UID for a VEVENT and a VTODO, if they originate from the same > entry in a database? Do you or anyone else know what the rules are > for this? Sorry it took me a while to test this - things have been crazy recently. From the release notes it looks like you already decided to generate unique UIDs for each source, which is fantastic - sounds like the safe thing to do, regardless of what the official spec requirements are. I'm happy to report that using UIDs fixes the issue I was seeing with duplicate entries in korganizer: http://bugs.kde.org/show_bug.cgi?id=99649 I'm going to restart gcaldaemon shortly - if it works then orgmode can boast unidirectional non-interactive syncing with google calendar! (as opposed to repeatedly importing an .ics file manually, which is very tedious).