Tickets :: Comment on [#11767] Kolab backend: All day events are not handled correctly

* Your Email Address
* Spam protection	Enter the letters below: . .._.. ..__..__ \| \| \| \|_/ \| \|\| \ \|/\\|_\|_\| \\|__\\|__/
Comment	> Hi, > > all day events are not handled correctly, at least not according to > the Kolab format specification. > > The Kolab definition of all day events: > -------------------------------------- > <event> > <start-date>(date or datetime)</start-date> > <end-date>(date or datetime)</end-date> > </event> > > -> So "start-date" and "end-date" allows "date" or "datetime" values. > > Later on the format specification clarifies: > "An event without a time but with a date associated is a full day > event. Such a full day event may span > over multiple days and may have recurrences." > > The earlier section "Common in Tasks and Events" is even more specific: > > "The start-date is optional for tasks. For events, it is required. If > they are there, they can either have a date or a datetime as the > type. Parsing this is just a matter of looking at the length of the > date string. In the case of an all day event (floating event) the > end-date MUST be in date only format." > > -------------------------------------- > > -> Right now kronolith saves all day events with a timestamp. Also it > fails to parse all day events from other Kolab clients correctly. We > should write out all day events with an "end-date" as "date" only. > > Thomas >
Attachment
Watch this ticket