I've been looking into why, when I sync my trusty old N900 with Google Calendar via CalDAV, the calendar shows "duplicate" events when I've changed an instance of a recurrence in Google Calendar. (One event will show with the old data, and one with the new data.)
Perhaps the answer would have been obvious if I knew the ical standard better. It seems that when Google records a changed instance, they add an event with the same global UID as the original one, and then uses RECURRENCE-ID to identify the particular instance. Since the Maemo 5 (Fremantle)'s calendar-backend does not store the global UID, that was bound to fail. (And, as far as I call tell, calendar-backend also only stores the RECURRENCE-ID if a RRULE is also present in the same event, which it isn't - and even when it stores the ID, it doesn't use it.) It looks like this calendar-backend will only honor RDATEs and EXDATEs, which must be stored in the original event (the one with the RRULE). Then, I suppose, the changed instances would look like single events to it. Is there any reasonable way SyncEvolution could do that conversion, so I won't have to keep scratching my head trying to remember which was the original, superseded event? _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
