[#11052] Kronolith creates unparsable ical file
Summary Kronolith creates unparsable ical file
Queue Kronolith
Queue Version 3.0.15
Type Bug
State No Feedback
Priority 1. Low
Owners
Requester grypho (at) tempus-vivit (dot) net
Created 03/05/2012 (442 days ago)
Due
Updated 04/27/2012 (389 days ago)
Assigned 04/05/2012 (411 days ago)
Resolved 04/27/2012 (389 days ago)
Attachments rule.png Download
Milestone
Patch No

History
04/27/2012 09:15:49 AM Jan Schneider State ⇒ No Feedback
 
04/05/2012 05:11:10 PM Jan Schneider Comment #2
State ⇒ Feedback		 Reply to this comment
Either this issue should be catched when the event is being entered
or the ical exporter should omit this empty list.
Kronolith already does that. If the event is saved with weekly 
recurrence, and no weekdays have been set, the weekday of the start 
date is used. How did you enter that event?
03/05/2012 10:05:28 AM grypho (at) tempus-vivit (dot) net Comment #1
State ⇒ Unconfirmed
New Attachment: rule.png Download
Patch ⇒ No
Milestone ⇒
Queue ⇒ Kronolith
Summary ⇒ Kronolith creates unparsable ical file
Type ⇒ Bug
Priority ⇒ 1. Low		 Reply to this comment
i everyone,

while playing with iCal4j under Android I discovered that  kronolith   
generates output which is violating RFC5545.

In the .ics file one of my appointments reads:

BEGIN:VEVENT
DTSTART:20111024T151500Z
DTEND:20111024T163000Z
DTSTAMP:20120304T202030Z

UID:20CD3890-7228-4D06-A305-3BF4A9B8EB69:E306E14E-FBB6-49FE-B37F-8CB3035CCB
18
CREATED:20111010T180609Z
LAST-MODIFIED:20111010T180609Z
SUMMARY:Test
CATEGORIES:Kalender
CLASS:PUBLIC
STATUS:CONFIRMED
TRANSP:OPAQUE
RRULE:FREQ=WEEKLY;INTERVAL=2;BYDAY=;UNTIL=20111219T225959Z
END:VEVENT

According to RFC5545 (http://tools.ietf.org/html/rfc5545#page-38),   
the RULE line is invalid as there is at least one list element 
expected when the BYDAY field is present.

Please see the attached screenshot which shows the event in kronolith.

I know, that rule does not make sense since there will be no   
repetitions when no weekday is selected BUT nevertheless this should   
not result in an unparsable ical file.

Either this issue should be catched when the event is being entered
or the ical exporter should omit this empty list.