[Tickets #2813] Remote Calendar Repeating Events

[bugs@bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/?id=2813
-----------------------------------------------------------------------
 Ticket             | 2813
 Updated By         | tmpone at thehillreaction.org
 Summary            | Remote Calendar Repeating Events
 Queue              | Kronolith
 Version            | 2.0.3
 State              | Feedback
 Priority           | 1. Low
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


tmpone at thehillreaction.org (2005-10-19 20:56) wrote:

> Test 1 has a recurring option that is currently not supported at all by 
> Kronolith. We only support recurrence end dates, not number of 
> recurrences.

OK

> Test 2 is displayed correctly. The iCalendar data says that the recurrence

> should end on the 12th.

I disagree. The actual iCal file can be downloaded from the URL
ical.mac.com/rchill548/KTest (I don't mean to imply you don't already know
this, I assume you have more practicle experience scheduling software than I
do - I'm just trying to provide complete info) and it shows the following
for event "Test 2":

UNTIL=20051012T035959Z

Since my current timezone is EDT (GMT - 0400), the event should be repeated
until 20051011T235959EDT.  The event should end befor 20051012.

When I display the event in Kronolith, it states:

Recur Until    	10/12/2005 12:00 am

Which I assume means midnight between 10/11 and 10/12.

It seems that Kronolith is adding 1 second to the UNTIL field when it
translates the iCAL entry, causing it to recur on 10/12, which seems
incorrect.

Furthermore (and I'm in over my head here), RFC 2445 says about the UNTIL
field:

The UNTIL rule part defines a date-time value which bounds the recurrence
rule in an inclusive manner. (I can't understand the intent of the next
sentence, so it may contradict what follows).

Even with the additional 1 second Kronolith seems to add in translation, I
would think the upper bound on this event would still be 20051012T040000Z or
20051012T000000EDT, so the event shown at 20051012T150000Z is still outside
the bounds given and so is incorrect.

If you remain unconvinced, you may mark this bug as closed. I have nothing
further to add.

Rob