Re: [SyncEvolution] Memotoo + montly recurrence + iCalendar 2.0
On Mi, 2011-01-19 at 08:03 +0000, Thomas Pequet wrote:
Hi Patrick
Ok I have add UID and RECCURENCE-ID in the CtCap.
Ok now the "Rx-Pref" and "Tx-Pref" are "text/calendar 2.0"
for Evolution.
I have no problem with the rules ... Each time I add one in Evolution,
the rule is added to Memotoo.
Are you sure ?
I can no longer reproduce it either. I see that UTC time in my normal
test cases is converted to local, floating time, but that is expected
given that MemoToo does not store time zone information.
After adapting my MemoToo test cases for that I was down to one
difference. It seems that when you added RECURRENCE-ID support, you did
it like that:
* add EXDATE to recurring VEVENT
* leave RECURRENCE-ID in the exception VEVENT
* *but* UID is not preserved (replaced with something that looks
like a sequential number, which is not necessarily globally
unique)
As a result, after syncing to a second client, the "remove whole
meeting" functionality does not work on that client. It is also not
possible to handle meeting updates received via email (ITIP), because
the UID specified in the email does not match the synchronized calendar.
Adding the EXDATE is probably a good idea for dumb clients, but wouldn't
be necessary when sticking to iCalendar 2.0. Is there a chance to keep
the UID as it is?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.