On Tue, 08 Dec 2009, Ohly, Patrick wrote: > On Tue, 2009-12-08 at 14:57 +0000, Chen, Congwu wrote: > > On Tue, 08 Dec 2009, Ohly, Patrick wrote: > > > On Tue, 2009-12-08 at 09:57 +0000, Chen Congwu wrote: > > > > > > The Evolution backend really can't import vCalendar 1.0. libical will > > > fail to parse it, because encoding rules are different. There might be > > > specific examples that happen to work, but this is not something that we > > > should count on. > > Er, the testing sample items for vcalendar 1.0 all have an 'iCalendar 2.0' > > type > > (config.insertItem, etc..). They are feed directly to the evolution > > backend. Does > > that mean all these sample items are guranteed to be correctly parsed by > > libical? > > Aren't all of these sample items really iCalendar 2.0, taken from > test/testcases/ical20.ics? That's true only for testItems > > Right now, every sync source must declare test data in its native > format. That's what the Evolution backend does, entirely independent of > the data format that is used when talking to the SyncML peer. Sure, I just was thinking the ical20 test cases may not suitable for vcalendar tests. With testItems we can change the test case file per peer, but not true for those built in cases. > > -- > 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. > >
-- Regards, Chen Congwu Moblin China Development _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
