On Thu, 2012-09-06 at 17:38 +0200, [email protected] wrote: > Ove Kåven <[email protected]> wrote on Wed, 05 Sep 2012 18:28:19 +0200: > > > If you explicitly configure the PC side to sync memos in text/calendar > > format instead of the default text/plain format > > > I did this, and I get a new error. Here is what I believe to be the > relevant snippet from the sync log on the PC:
What is your SyncEvolution version on the PC? text/calendar format (aka iCalendar 2.0) support for VJOURNAL was added in 1.99.1.1. Your version doesn't seem to support it. Or there is an issue with the line breaks. It's a bit odd that it seems to combined two lines into one in this error message: parseMimeDir: property not parsed (unknown or not storable): BEGIN:VJOURNAL LAST-MODIFIED: FWIW, the incoming data has normal \n line breaks, not \r\n. > [2012-09-06 17:08:01.320] 'ScriptExecute' - Start executing Script, > name=beforewritescript [--][++] [->end] [->enclosing] > [2012-09-06 17:08:01.321] SYSYNC wbxmlVersion: smlErr 0x200A (Incompatible > WBXML Content Format Version) while parsing > [2012-09-06 17:08:01.321] SYSYNC - parsing UNKNOWN token, ext=undef/SyncML > [2012-09-06 17:08:01.321] SYSYNC - Tag start at 0x0, scanner pos at > 0x241C270, data: > [2012-09-06 17:08:01.321] SYSYNC 42 45 47 49 4E 3A 56 43 41 4C 45 4E 44 41 52 > 0D 0A 56 45 52 53 49 4F 4E 3A 32 2E 30 0D 0A 50 52 > [2012-09-06 17:08:01.321] SYSYNC BEGIN:VCALENDAR__VERSION:2.0__PR I couldn't reproduce that here. It doesn't seem related to the parsing error. -- 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
