On So, 2010-12-26 at 20:18 +0000, Irihapeti wrote: > On 26/12/10 23:27, Patrick Ohly wrote: > > Can you confirm that the line that he suggested works for you, instead > > of removing it entirely? > > > > if (ISAVAILABLE(SUMMARY)!=TRUE && DESCRIPTION==EMPTY) > > DESCRIPTION=SUMMARY; > > That line seems to work. I've tested with items originating on the > phone and on Evolution.
I've changed it on the master branch (will be in 1.2): commit f229dabb176eb4dc2d46ee6f8f8f565e40379c17 Author: Patrick Ohly <[email protected]> Date: Sun Dec 26 21:50:36 2010 +0100 XML config: avoid duplicating SUMMARY as DESCRIPTION When sending a calendar event or task to a peer, the DESCRIPTION is now only set to the SUMMARY in cases where the peer is known to not support the SUMMARY property. This is an improvement over the original logic which always duplicated the text. When receiving such an item, a DESCRIPTION which is identical to the SUMMARY is removed. This restores the original logic from upstream Synthesis configs. Since commit ca22c2d4c45136d543419bfb98f356aef1e3ff88, SyncEvolution avoided empty DESCRIPTION fields by setting the DESCRIPTION to the SUMMARY because libical was unhappy about it; but that was already successfully avoided by another change in that commit, so it makes sense to avoid storing duplicate data, should the peer send it (from a previous sync or because it always sends the same text in both properties). -- 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] http://lists.syncevolution.org/listinfo/syncevolution
