---- Reported by patrick.ohly@intel.com 2010-12-13 05:59:15 +0000 ---- When running as server, the Synthesis engine should be able to merge an update that it receives from a phone such that additional fields (like CATEGORY) are preserved, because the engine knows that the peer only supports plain text. When running with the Evolution Data Server backend, the additional properties were lost. The reason is that the backend does the plain text<->VJOURNAL conversion. This conversion should be left to the engine. It would also allow automatic format negotiation for memos (use plain text with most peers, VJOURNAL between SyncEvolution instances). The necessary changes are (from memory, unverified): - configure plain text datatype which uses same field list as calendar - change EDS backend to use it --- Bug imported by patrick.ohly@gmx.de 2012-07-29 20:36 UTC --- This bug was previously known as _bug_ 11251 at https://bugs.meego.com/show_bug.cgi?id=11251
Done for CalDAV, still to be done for EDS backend post 1.3. commit 16e0b4af191fda9c4d2a8f981d5c2513fb818d11 Author: Patrick Ohly <patrick.ohly@intel.com> Date: Fri Jun 15 12:09:07 2012 +0200 WebDAV: exchange VJOURNAL as iCalendar 2.0 or plain text Use the new "text/calendar+plain" type so that "caldavjournal" can be used with peers which do not support iCalendar 2.0 for memos. commit 92d7e7cc489b7251a122bf2b1eccec3fab6f576c Author: Patrick Ohly <patrick.ohly@intel.com> Date: Fri Jun 15 12:07:46 2012 +0200 engine: support VJOURNAL and VJOURNAL+text/plain The "text/calendar" type now also contains rules for parsing and generating VJOURNAL in iCalendar 2.0 and vCalendar 1.0. When using "text/calendar+plain", the internal format is iCalendar 2.0 with plain text used as alternative if the sync peer does not support VJOURNAL for memos. These types can be used as "databaseFormat" of the file backend and by other backends which want to replace plain text as exchange format for memos.
Now also done for EDS, see 1.4.99.4.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.