Hello! According to its CtCap, Memotoo supports the X-EVOLUTION-FILE-AS extension: http://syncev.meego.com/2011-08-17-18-20_synthesis_memotoo_mobical_google_apple_davical_googlecalendar_testing/head-testing-amd64/18-memotoo/Client_Sync_eds_contact_testExtensions.patch.client.A/syncevolution-log_trm001_002_incoming.xml
But it seems to get lost, which breaks the testExtensions test. This is provided by Evolution: BEGIN:VCARD VERSION:3.0 NICKNAME:user15 NOTE:Spouse's Name: foobar FN:spouse name N:name;spouse;;; X-EVOLUTION-FILE-AS:spouse\, name UID:pas-id-4E4C7EDE00000180 REV:2011-08-18T02:54:22Z END:VCARD This is sent to Memotoo as: BEGIN:VCARD VERSION:2.1 REV:20110818T025422Z N:name;spouse;;; FN:spouse name X-EVOLUTION-FILE-AS:spouse, name X-GENDER: NICKNAME:user15 TITLE: ORG:;;; ROLE: TEL: EMAIL: URL: X-MOZILLA-HTML: ADR:;;;;;; BDAY: NOTE:Spouse's Name: foobar PHOTO: END:VCARD http://syncev.meego.com/2011-08-17-18-20_synthesis_memotoo_mobical_google_apple_davical_googlecalendar_testing/head-testing-amd64/18-memotoo/Client_Sync_eds_contact_testExtensions.send.client.A/syncevolution-log.html Note that the comma was not considered special by the Synthesis encoder. My memory is a bit fuzzy: is escaping it optional in vCard 3.0 optional and/or does this depend on whether the property is meant to be a comma-separated list? Lukas? What comes back has an no X-EVOLUTION-FILE-AS: BEGIN:VCARD VERSION:3.0 REV:20110818T025434Z N:name;spouse;;; FN:name spouse NICKNAME:user15 NOTE:Spouse's Name: foobar END:VCARD http://syncev.meego.com/2011-08-17-18-20_synthesis_memotoo_mobical_google_apple_davical_googlecalendar_testing/head-testing-amd64/18-memotoo/Client_Sync_eds_contact_testExtensions.refresh.client.B/syncevolution-log.html Thomas, Memotoo either has to preserve the property or must not declare support for it in the CtCap. -- 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
