Hi,
I have dug into the multisync source code, solely for curiosity.
I found out that you use libversit to parse vCalendar version 2.0, aka
iCalendar (RFC 2445). I must say that this is a really bad idea as
libversit only knows about vCalendar 1.0 that diverge enough from 2.0.
That include recurrent events (seems to be reading lot of problem
reports with that), encoding (vCalendar 1.0 as not been designed with
non-ASCII charset in mind). May I suggest to switch to libical and use
vCalendar 2.0 internally for any calendaring / todo information ? This
is already what Evolution uses.
libical:
http://www.softwarestudio.org/libical/
The benefit would be: standard data model for calendaring, that handles
all what we'd want.
Then any device emitting vCalendar 1.0 calendaring info would just need
conversion to iCalendar before sending to the sync engine. (libicalvcal
in libical is meant to do that, but it is hackish).
Correct me if I'm wrong.
Hub
--
"<erno> hm. I've lost a machine.. literally _lost_. it responds to ping,
it works completely, I just can't figure out where in my apartment it
is." -- http://www.bash.org/?5273
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Multisync-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/multisync-devel
