From: Patrick O. <Pat...@gm...> - 2008-05-15 16:52:26
|
On Tue, 2008-05-13 at 20:38 +0200, Patrick Ohly wrote: > > By what i have be seen syncevolution worked with iCalendar and > > funambol > > with Vcalendar, so i think it is a problem of interpretation. > > This is one of the known problems in that combination: > http://www.estamos.de/projects/SyncML/Compatibility.html#Compatible+SyncML+Servers > > SyncEvolution and Evolution itself use the iCalendar 2.0 format > for events and todos. myFUNAMBOL uses vCalendar 1.0. Both have > some support for parsing incoming items in the other format, so > exchanging data is possible in principle, but be prepared to run > into problems: > > * Time zone information is sent by SyncEvolution, but not > used by myFUNAMBOL and not preserved. Make sure that > client and server are set to the same time zone to > mitigate the problem. This is not going to help with > events which were scheduled in different time zones. As mentioned by Andrea, this issue is scheduled to be fixed with the next Funambol release, but in the meantime I received answers to my mail on the developers list and ... > * Importing items with special characters into Evolution > scrambles these characters because Evolution does not > handle the vCalendar 1.0 encoding of these characters. > * Sending such items with a broken encoding back to the > server can cause a parser exception on the server. ... there are no plans to support communication between client and server using iCalendar 2.0. This means these two problems will continue to exist. > * Alarms get lost, probably regardless in which direction > the events are sent. This problem also will persist. > * The information that an event is an all-day event gets > lost. Might be fixed as part of the time zone work. -- Bye, Patrick Ohly -- Pat...@gm... http://www.estamos.de/ |