[Tickets #5250] Re: Funambol to Kronolith, recur_enddate timezone issue

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/5250
-----------------------------------------------------------------------
 Ticket             | 5250
 Updated By         | Jan Schneider <jan at horde.org>
 Summary            | Funambol to Kronolith, recur_enddate timezone issue
 Queue              | SyncML
 Type               | Bug
-State              | Assigned
+State              | Feedback
 Priority           | 2. Medium
 Milestone          |
 Patch              |
-Owners             | Karsten Fourmont
+Owners             |
-----------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2008-04-09 11:13) wrote:

I can't reproduce anymore, because Funambol sends both the number of
occurrences (calculated from the recurrence end) and the recurrence end
date. Since number of occurrences has precedence now in the Horde code,
such events are converted now to recurrence rules like:
RRULE:FREQ=WEEKLY;COUNT=10;INTERVAL=1;BYDAY=WE

Beside that, the date stamp sent by the client is a perfectly valid ISO
date time string. If it's not correctly translated to the local timezone,
this has to be fixed either in the iCalendar library or in Kronolith, but
definitely not in the Sync4j device handler.

Can you please try if you still see this with the latest code from CVS or
the next RCs?