On Wed, 2003-09-24 at 16:42, Hubert Figuiere wrote:
> Hi,
Hello
> 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.
I agree. The libical functionality would help in any plugin-specifig
transforms too.
Something to keep in mind is that at the moment the evolution plugin
links agains libical-evolution already. So if you want to play around
with libical, you should either use that or change the evo plugin to use
plain libical (which it might not be able to do if it relies on
libical-evolution specific behaviour).
I didn't realise this at first at gor bit by different library versions
being used at runtime depending on whether I'd included the evo plugin
or not :-/
Mika Raento
--
Mika Raento mailto:[EMAIL PROTECTED] http://www.iki.fi/mikie/
"You can't *ADD* things and come out with *LESS* than you started with!"
"I can do that! It's a free country! I've got my rights!"
-from Calvin & Hobbes by Watterson
-------------------------------------------------------
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
