OS: Windows CE
When creating a Groupware object, e.g an event, the last-modification-time
violates the Kolab Format for Storage 2.0: http://kolab.org/doc/kolabformat-2.0-html/x147.html#AEN167
only allows for YYYY-MM-DDThh:mm:ssZ, but created appointmens
with Windows CE from CAB 20101213 create something with "+00:00" instead of the "Z", example:
<product-id>Akonadi 1.4.81, Kolab resource</product-id>
the defect also shows on other platforms.
Create the object in a kolab folder, look at the raw stored object.
Cna also be seen with Kontact Desktop E5: kdepim
The code that creates the last-modifcation-date tag looks basically like this:
lastModified().toZone( mZone ).toString( KDateTime::ISODate )
where lastModified() returns a KDateTime object and mZone is the KTimeZone object of this calendar.
Although '+00:00' seems to be identically to 'Z' from a logical point of view there is some difference (that I didn't get) according to the RFC.
@John can you shed some light on this issue? Has something changed in the time handling/formatting code lately?
the point is that the Kolab Storage format 2.0 does not allow to deviate
from the 'Z' variant. The defect might be in there for a long while maybe since
KDE SC 4.0 was coming up.
SVN commit 1206670 by tokoe:
Always write out the creation-date and last-modification-date
in Zulu time to be compatible with Kolab storage format.
M +2 -3 kolabbase.cpp
WebSVN link: http://websvn.kde.org/?view=rev&revision=1206670
Kontact Touch Windows CE 2011-02-11
Looked at the kolab.xml of a new created event.
It contains Z in dates. Okay.