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

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12489
------------------------------------------------------------------------------
  Ticket             | 12489
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | DTEND incremented on ical export for no real reason
  Queue              | Kronolith
  Version            | 4.1.2
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2013-07-24 16:14) wrote:

> 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.