http://bugs.meego.com/show_bug.cgi?id=2764
pohly <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #3 from pohly <[email protected]> 2010-06-08 09:39:59 PDT --- Here's the event as it is passed from the Maemo calendar backend into SyncEvolution: BEGIN:VCALENDAR VERSION:1.0 PRODID://Nokia Corporation//Maemo5 Calendar PR1.2//EN BEGIN:VEVENT CREATED:20100608T121236Z SUMMARY;ENCODING=QUOTED-PRINTABLE;CHARSET=UTF-8:= N900=20h=C3=A4ly UID:2438 DTSTART:20100608T123500Z DTEND:20100608T133500Z ATTACH: SEQUENCE:0 LAST-MODIFIED:20100608T121236Z BEGIN:VALARM TRIGGER;VALUE=DATE-TIME:20100608T153000 DURATION:PT2M REPEAT:1 ACTION:AUDIO END:VALARM END:VEVENT END:VCALENDAR That's bogus. VALARM is not part of vCalendar, which this item pretends to be (VERSION:1.0). Okay, the Synthesis parser ignores that. The next problem is timezone related. The event itself uses UTC time, but the alarm uses local time without specifying the offset against UTC (3 hours in this case). Finally, the alarm was marked as audio alarm, without specifying which kind of sound is meant to be played. Synthesis inserts a default "alarm" here. It's hard to tell what a valid specifier could be; the vCalendar standard only mentions that a local file could be referenced, which is not particularly helpful for an interchange format. What is finally sent to GooSync is this: BEGIN:VCALENDAR VERSION:1.0 TZ:+00:00 DAYLIGHT:FALSE BEGIN:VEVENT LAST-MODIFIED:20100608T121236Z UID:2438 SEQUENCE:0 SUMMARY;CHARSET=UTF-8:N900 häly DESCRIPTION;CHARSET=UTF-8:N900 häly DTSTART:20100608T123500Z DTEND:20100608T133500Z AALARM:20100608T153000;;1;alarm DALARM:20100608T153000;;1;alarm END:VEVENT END:VCALENDAR Regarding the event sent to the N900, I think it is this one: BEGIN:VCALENDAR VERSION:1.0 BEGIN:VEVENT DTSTART:20100608T113000Z DTEND:20100608T123000Z SUMMARY;ENCODING=QUOTED-PRINTABLE;CHARSET=UTF-8:Testi h=C3=A4ly google TRANSP:0 CLASS:PUBLIC END:VEVENT END:VCALENDAR There's simply no alarm information at all here. So basically the questions to the GooSync operators is: a) why do they not send alarm information to us and b) in which format do they accept alarms? Would you mind asking them? Feel free to point them to this bug report or tell them to contact me. I don't know anyone at GooSync myself. You are at least a paying (?) customer. -- Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
