Recurring events with timezone

[Andrew McMillan]

On Tue, 2010-10-19 at 05:54 +0200, Joon Radley wrote:
> Hi Hendrik,
> 
> There is no reason for this time zone information to be added.
> 
> The format is universal and the client should adjust UTC to fit the
> users locale.
> 
> All other Kolab clients have been able to successfully implement the
> UTC concept.

Hi Joon,

Did you read the previous messages in this thread?

Storing time without timezone *fails* for repeating events which are
intended to be localised to a particular timezone for calculation of
future instances.

For example, could you please tell me exactly when, in UTC, each of the
twelve instances next year will occur for a monthly meeting which was
initially scheduled for the 9:00am on the 1st of the January this year
in a timezone which (at that time) was aligned with UTC.

Certainly it would be possible to store some limited set of recurring
instances on creation of the event, though that is obviously a lossy
operation. Especially for events which are set to recur forever.

Other calendaring software (optionally) records timezones per event for
this and other reasons (I don't always want an event localised to my
current timezone: sometimes I want it to be localised to the timezone I
will be in when it will happen), so sure if Kolab clients generally are
broken that's only a kolab problem.

This project that Hendrik is talking about is one that involves Kolab
*interoperating* with client software which is not broken in that way,
specifically Evolution.

Regards,
					Andrew McMillan.

-- 
------------------------------------------------------------------------
andrew (AT) morphoss (DOT) com                            +64(272)DEBIAN
        Freedom of the press is for those who happen to own one.
------------------------------------------------------------------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.kolab.org/pipermail/format/attachments/20101019/5b295d26/attachment.sig>