[Tickets #1365] NEW: end date for recurring events not supported

[bugs at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/?id=1365
-----------------------------------------------------------------------
 Ticket             | 1365
 Created By         | gauret at free.fr
 Summary            | end date for recurring events not supported
 Queue              | Kronolith
 Version            | 2.0.2
 State              | Unconfirmed
 Priority           | 1. Low
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


gauret at free.fr (2005-02-13 07:23) wrote:

When importing from ICalendar files, Kronolith ignores the end date for
recurring events. Example :
BEGIN:VEVENT
DTSTAMP:20050213T151539Z
CREATED:20050213T151408Z
SEQUENCE:2
LAST-MODIFIED:20050213T151536Z
SUMMARY:test recurring event
CLASS:PUBLIC
PRIORITY:3
RRULE:FREQ=DAILY;UNTIL=20050218;INTERVAL=1
DTSTART;VALUE=DATE:20050214
DTEND;VALUE=DATE:20050215
TRANSP:OPAQUE
END:VEVENT

This event is supposed to happen every day (INTERVAL=1) until 2005-02-18.
The UNTIL statement is ignored by Kronolith, and thus the events happens
every day from day start.

This statement is part of the iCalendar standard as defined in RFC 2445 :
http://www.faqs.org/rfcs/rfc2445.html
See paragraph 4.3.10 about recurring events.
It would be nice if COUNT statements were also supported.

I'm not sure if this sould be filed as bug or enhancement, but since those
statements are part of the standard, I chose bug.

Thanks