On Thu, 2013-04-18 at 11:22 -0700, Diane Trout wrote:
> Accessing items with
> will work, because that passes the item content through unmodified.
> However, syncing will not work because it needs to convert between the
> format used by the storage and the internal representation ("field
> What does this application/x-vnd.akonadi.calendar.todo format look like?
> Are there KDE utility classes for parsing and generating it?
> And finally, do you think you could add support for this format, with
> some help of course?
I can try.
The file looks mostly like [iv]Cal.
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
I made a couple of test todos and did "syncevolution --export -
todo", loaded the result into vi and pasted into the email. (nicely
demonstrating the inconsistent eol marks).
That won't matter to the Synthesis parser, it treats both alike.
The KDE Pim tools support hierarchical todos which seemed like an
feature. I'm not sure if RELATED-TO: is a non-standard attribute.
It's a standard attribute, but not currently supported by the Synthesis
configuration used by SyncEvolution.
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.