[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kolab-format
Subject:    Re: Timezone issues
From:       Martin Konold <martin.konold () erfrakon ! de>
Date:       2008-06-03 14:49:33
Message-ID: 484559FD.9040900 () erfrakon ! de
[Download RAW message or body]

Bernhard Reiter wrote:

Hi Bernhard,

>> I tend to disagree with this statement. IMHO the location Berlin is always
>> GMT+1 independent of DST. In general DST does NOT affect the timezone. The
>> later is only affected by the location.
> Common explanations tend to differ from your view:
>   
I guess that this is due to some language inaccuracies.

> We would need to change the datetime definition then to include timezone
> information and we would need to come up with a good definition for timezone.
> As this forces a massive change on all clients, I believe we should propose 
> something for beyond the 2.0 spec, which is stable as it is (and having the 
> shortcomings that is has).
>   

I don't see the massive change as current clients seem not to really 
care or implement smart/correct timezone and DST handling.

>> Why is a recurring event like weekly on Mondays at 2pm a rare use case?
>>     
>
> Well, it is not. But people argued somehow that this was not happening
> due to calculations when the appointment was made.
>   
So how is a reccuring event which happens daily at noon expressed in our 
xml according to your view?

> I remembered testing this stuff Toltec and Kontact back and forth 
> and it used to work.
>   
Did you also cover events which got created before the DST change and 
then looked at them after the DST change?

Yours,
-- martin

_______________________________________________
Kolab-format mailing list
Kolab-format@kolab.org
https://kolab.org/mailman/listinfo/kolab-format
[prev in list] [next in list] [prev in thread] [next in thread]