[Tickets #5235] Re: Internal kolab time encoding

[bugs at bugs.horde.org]

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

Ticket URL: http://dev.horde.org/horde/whups/ticket/?id=5235
-----------------------------------------------------------------------
 Ticket             | 5235
 Updated By         | Gunnar Wrobel <p at rdus.de>
 Summary            | Internal kolab time encoding
 Queue              | Horde Framework Packages
 Version            | HEAD
 Type               | Bug
 State              | Assigned
 Priority           | 1. Low
 Owners             | Gunnar Wrobel
-----------------------------------------------------------------------


Gunnar Wrobel <p at rdus.de> (2007-05-08 06:02) wrote:

I checked the way Bug 1822 was handled but I'm pretty confident that the
fix applied there was indeed correct.

Kronolith uses the local timezone internally. And Kolab wishes to have all
day events remembered by their date only (no additional time information).
For an all day event that would occur today Kronolith sets the start date
to 0:00 08/05/2007 (local time). If the Kolab driver would now use
gmstrftime to generate a date string from this timepoint, this would
result in 2007-05-07 since 0:00 08/05/2007 local time is 10:00 07/05/2007
GMT. I tested that whole day events are actually misplaced a day to early
if I apply the patch.