[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Orgmode] .ics export violates RFC2445
From: |
Adam Spiers |
Subject: |
Re: [Orgmode] .ics export violates RFC2445 |
Date: |
Tue, 27 May 2008 22:55:57 +0100 |
User-agent: |
Mutt/1.5.14 (2007-02-12) |
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).
- Re: [Orgmode] .ics export violates RFC2445, Carsten Dominik, 2008/05/15
- Re: [Orgmode] .ics export violates RFC2445,
Adam Spiers <=
- 1-way syncing with google calendar (was Re: [Orgmode] .ics export violates RFC2445), Adam Spiers, 2008/05/27
- [Orgmode] Re: 1-way syncing with google calendar (was Re: .ics export violates RFC2445), Cezar Halmagean, 2008/05/28
- Re: [Orgmode] Re: 1-way syncing with google calendar (was Re: .ics export violates RFC2445), Adam Spiers, 2008/05/28
- Re: [Orgmode] Re: 1-way syncing with google calendar (was Re: .ics export violates RFC2445), Tim O'Callaghan, 2008/05/29
- Re: [Orgmode] Re: 1-way syncing with google calendar, David Smith, 2008/05/30
- Re: [Orgmode] Re: 1-way syncing with google calendar, Adam Spiers, 2008/05/30