Hello, While I am tesing vcal1.0 format, I found it is nearly impossible to compare a vcalendar 1.0 item and a icalendar 2.0 item. The root cause is, we always tell Synthesis to transform its data as "icalendar 2.0" before storing into our Evolution backend. Discussed with Patrick and the problem is the underlying Evolution Backend do not support 'vcalendar 1.0' type. However I think at least it can accept 'vcalendar 1.0' items and correctly interpret and store it as 'icalendar 2.0', isn't it? Or this is something handled by our Evolution backend? If it really accepts 'vcalendar 1.0' input, not letting synthesis feeding it 'vcalendar 1.0' types perhaps is for efficiency considerations? i.e. The transforamtion 'Synthesis internal' -> 'icalendar 1.0' -> 'vcalendar 2.0' is a bit too long and productless. But it indeed has some textual differences with the other approach : 'Synthesis internal' -> 'icaledar 2.0'. At least for testing purposes, I would suggest the long transorming approach, it makes synccompare a bit easier. -- Regards, Chen Congwu Moblin China Development