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

List:       kde-pim
Subject:    RE: [Kde-pim] Timezones and resources
From:       "Best, Jan-Pascal van" <j.p.vanbest () tbm ! tudelft ! nl>
Date:       2003-11-28 14:53:03
[Download RAW message or body]

> Thanks for the explanation. What should happen when the user 
> changes the time zone while a calendar is loaded? Shouldn't all
> Event objects in all resources then be updated for the new time 
> zone? This doesn't happen now..

And you can cause timezone problems with it...

If you set the time zone to Amsterdam and create an appointment
like this (9:00 CET=Amsterdam time equals 8:00 UTC) in a local
calendar (.ics file):

	BEGIN:VCALENDAR
	PRODID:-//K Desktop Environment//NONSGML KOrganizer 3.2 beta2//EN
	BEGIN:VCALENDAR
	PRODID:-//K Desktop Environment//NONSGML KOrganizer 3.2 beta2//EN
	VERSION:2.0
	BEGIN:VEVENT
	DTSTAMP:20031128T143623Z
	ORGANIZER:MAILTO:nobody@nowhere
	CREATED:20031128T143616Z
	UID:KOrganizer-1820055893.722
	SEQUENCE:0
	LAST-MODIFIED:20031128T143616Z
	SUMMARY:9:00 Amsterdam
	CLASS:PUBLIC
	PRIORITY:3
	DTSTART:20031128T080000Z
	DTEND:20031128T090000Z
	TRANSP:OPAQUE
	END:VEVENT

	END:VCALENDAR

Then you open the calendar, change the time zone to
London (UTC at the moment), edit the appointment (not sure
if that is necessary) and close korganizer, the appointment
is moved an hour, to 9:00 London time!

	BEGIN:VCALENDAR
	PRODID:-//K Desktop Environment//NONSGML KOrganizer 3.2 beta2//EN
	VERSION:2.0
	BEGIN:VEVENT
	DTSTAMP:20031128T153740Z
	ORGANIZER:MAILTO:nobody@nowhere
	CREATED:20031128T153616Z
	UID:KOrganizer-1820055893.722
	SEQUENCE:0
	LAST-MODIFIED:20031128T153616Z
	SUMMARY:9:00 Amsterdam
	CLASS:PUBLIC
	PRIORITY:3
	DTSTART:20031128T090000Z
	DTEND:20031128T100000Z
	TRANSP:OPAQUE
	END:VEVENT

	END:VCALENDAR

It's a bit of a pathetic case, but it could happen when people travel around and change 
KOrganizer's time zone. We could avoid it by changing the time zone of all Event objects 
loaded when setTimeZoneId() is called, or by changing the semantics altogether, having 
all resources deliver UTC Events, and letting the KOrganizer GUI sort it out. The latter 
solution seems more clean, but I suppose it would mean a lot of changes in KOrganizer...

Jan-Pascal

_______________________________________________
kde-pim mailing list
kde-pim@mail.kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/

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