On Thu, 2013-04-25 at 00:41 -0700, Diane Trout wrote: > > 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.
That makes sense. Looking at the SyncEvolution source, I see that it already uses application/x-vnd.akonadi.<something> for events and memos, just not for tasks. That seems like an oversight, so your patch is the right solution. I've committed it with you as author. Will be in 1.3.99.4. -- 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. _______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
