> Right. I wonder what the difference is, because I fail to see one in the > quoted examples. Handling those extensions while syncing can become > tricky. If they cannot be mapped to iCalendar 2.0, then at least the > Synthesis field list and Synthesis profile for iCalendar 2.0 should > support them, because otherwise the extensions will get lost when > updating an item in Akonadi. > > For the iCalendar 2.0 subset, syncing should already work with your > patch. If there are Akonadi resources using "text/calendar" with VTODO, > then a better solution would be to search for both by expanding the > parameter given to the AkonadiSyncSource from a single-value string to a > list.
So after the tiny patch I made todos seem to have synced correctly. I went looking through the kdepimlibs source code to see if I could understand why they're using the x-vnd mime type. Ok I got a reference from #akonadi. They used the different mime types to "differentiate between events, journals and todo entries; there's a different mime type for each and text/calendar is a bit vague." "Externally those are all ot be treated as text/calendar". Through the freedesktop shared-mime-info system they declared the application/x-vnd.akonadi types as subtypes of the standard text/calendar type. And if you want to double check I found their test data at: http://quickgit.kde.org/?p=kdepimlibs.git&a=tree&h=f4202c8fc8cb0e6c9047119b9ae09d06f431863a&hb=be213b813ecf60179c48fb40d27a6b120ac92821&f=kcalcore%2Ftests%2Fdata Diane _______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
