http://bugs.meego.com/show_bug.cgi?id=10092
pohly <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO --- Comment #6 from pohly <[email protected]> 2010-12-13 07:50:17 PST --- (In reply to comment #4) > (In reply to comment #3) > > Not sure how to work around this. One possibility would be to remove the end > > date before sending to the phone, but that changes the semantic of the > > event. > > i agree, this is not the right way to handle it > > > Do events with a repeat count ("repeat for x occurrences" instead of "repeat > > until xyz") work with the phone? That might be a better workaround. > > Yes, they work: > > While RRULE:FREQ=DAILY;COUNT=4 does the job, RRULE:FREQ=DAILY;UNTIL=20101120 > only shows the first event on the phone. I think I fixed this issue as part of bug #11241, without realizing it at first. The root cause of #11241 is that UNTIL=20101120 in iCalendar 2.0 leads to an invalid RRULE being sent in the vCalendar 1.0 item. COUNT=4 takes a slightly different code path and ends up sending a valid RRULE (bug #11241 comment #1). Can you try this with the SyncEvolution 1.1.0.99.1 that I am going to release this week? I'll announce it on mailing list. -- Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
