[Tickets #11695] Kolab backend: Datetime fields from/to Kolab XML are not in UTC

bugs at horde.org bugs at horde.org
Tue Nov 13 09:38:37 UTC 2012


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

Ticket URL: http://bugs.horde.org/ticket/11695
------------------------------------------------------------------------------
  Ticket             | 11695
  Created By         | Thomas Jarosch <thomas.jarosch at intra2net.com>
  Summary            | Kolab backend: Datetime fields from/to Kolab XML are
                     | not in UTC
  Queue              | Kronolith
  Version            | Git master
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Thomas Jarosch <thomas.jarosch at intra2net.com> (2012-11-13 09:38) wrote:

Hi,

according to the Kolab format specification, all datetime fields  
should be stored as UTC:

--------------------
Datetime YYYY-MM-DDThh:mm:ssZ. The T is the literal char, and always  
needs to be between the
date and the time. The Z is also the literal char, and shows that the  
datetime is UTC. The format does
not allow for other time settings than UTC. An example could be  
2004-05-04T15:00:00Z.
--------------------

Right now kronolith stores localtime. This results in interoperability  
problems with other Kolab clients :)
kronolith of H4 works correctly.

Cheers,
Thomas






More information about the bugs mailing list