Hello! I am testing SyncEvolution<->http://www.plan44.ch/fsync_nightly. One of the tests involves X- extensions. The server seems to support some of them, probably using wild card matching.
Here's what is sent to it: BEGIN:VCARD VERSION:3.0 PRODID:-//Synthesis AG//NONSGML SyncML Engine V3.4.0.27//EN REV:20110817T213114Z N:Doe;John;;; [...] X-FOOBAR-EXTENSION;X-FOOBAR-PARAMETER=foobar:has to be stored internally by engine and preserved in testExtensions test; never sent to a peer X-TEST;PARAMETER2="quoted because of spaces";PARAMETER1=nonquoted:Content with\nMultiple\nText lines\nand national chars: äöü END:VCARD http://syncev.meego.com/2011-08-17-18-20_synthesis_memotoo_mobical_google_apple_davical_googlecalendar_testing/head-testing-amd64/13-synthesis/Client_Sync_eds_contact_testItems.send.client.A/syncevolution-log.html This comes back: BEGIN:VCARD VERSION:2.1 REV:20110817T213120Z N:Doe;John;;; [...] X-FOOBAR-EXTENSION;X-FOOBAR-PARAMETER=foobar:has to be stored internally by engine and preserved in testExtensions test; never sent to a peer X-TEST;PARAMETER2="quoted because of spaces";PARAMETER1=nonquoted;CHARSET=UTF-8;ENCODING=QUOTED-PRINTABLE:Conte nt with=0D=0A= Multiple=0D=0A= Text lines=0D=0A= and national chars: =C3=A4=C3=B6=C3=BC END:VCARD http://syncev.meego.com/2011-08-17-18-20_synthesis_memotoo_mobical_google_apple_davical_googlecalendar_testing/head-testing-amd64/13-synthesis/Client_Sync_eds_contact_testItems.refresh.client.B/syncevolution-log.html Note that X-TEST uses quoted-printable, but then it inserts a space into the middle of the word "Content". The parser in the client correctly (?) preserves that space, so the text that is stored in Evolution becomes "Conte nt". To me this looks like one of those cases where a vCard 2.1 encoder is stuck between a stone and a hard place: write a line longer than desired or insert a space. IMHO it should choose to write a longer line. I bet most parsers would cope with it just fine, whereas inserting the space definitely has user-visible effects. SyncEvolution disables folding, there have been no problems reported because of that. I'm going to get the test working by replacing "Content" with "Text", which allows the encoder to fold the line without an extra space. Just wanted to mention the problem... -- 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. _______________________________________________ os-libsynthesis mailing list [email protected] http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
