Recurring events with timezone

Hendrik Helwich h.helwich at
Wed Oct 27 10:01:45 CEST 2010

Am Dienstag, 26 Oktober 2010 18:35:45 schrieb Shawn Walker:
> Personally, I don't think timezone in the kolab format should be needed. 
> No matter where in the world the user is regardless of the user's timezone,
> the time is the same in UTC.  Converting a time from "local -> UTC ->
> local" doesn't make any sense UTC is the same as the UTC time in the kolab
> format.
> I know there are discussions about recurring event is not displaying
> correctly when crossing over daylight/standard time, but that is a bug in
> the client application for not accounting the cross over for the
> daylight/standard time.

Hi Shawn,

no it is a bug in the format because it does not hold all the information (TZ) 
which is needed for calculating the correct time (please see the examples in 
this thread).

> And for the webclient where the server doesn't know what timezone the user
> is in, the webclient need to have the user specify what timezone that they
> are in so that the server can adjust the UTC time correctly to the user's
> timezone that they have configured to.

Yes you are right this would make sense. But this is not the problem which was 
discussed in this thread before.

Best Regards,


> On 10/26/2010 9:27 AM, Hendrik Helwich wrote:
> > Hello,
> >
> > the discussion here on adding timezone information to the kolab format
> > has stopped.
> > What do you think about adding timezone information to the kolab format?
> > I would be glad for any feedback on this point :-)
> > Should we assume that the kolab format will stay as it is right now and
> > time zones will not be added in the near future?
> > In this case we will need to make a hack for dealing with the timezone
> > problem in the kolab format. Is there a recommended way for doing this?
> >
> > Regards,
> > Hendrik
> >

More information about the format mailing list