Tickets :: Comment on [#12489] DTEND incremented on ical export for no real reason

* Your Email Address
* Spam protection	Enter the letters below: .__ .__ ._..__ .__ \| \[__) \| \| \[__) \|__/\| _\|_\|__/[__)
Comment	>> Here $end->sec is incremented with the intention, that DTEND MUST be >> later than DTSTART. But it is incremented whether it's neccessary or >> not. If DTEND already IS later than DTSTART, a second will be added >> on every ical export. > > No, this is not the reason it is incremented. According to RFC 2445 > the DTEND field is a non-inclusive. In other words, the actual event > ends one second BEFORE the value of DTEND. Kronolith, on the other > hand stores the event end time as an inclusive value, i.e., the event > ends exactly on the second specified. We therefore have to increment > the DTEND value by one second so that the value presented in the iCal > file is non-inclusive.
Attachment
Watch this ticket