Bug 151681

Summary:	different timezones in one ical file are not recognised
Product:	[Applications] korganizer	Reporter:	Bart Geesink <bart>
Component:	general	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Bart Geesink 2007-11-01 10:07:41 UTC

Version:            (using KDE KDE 3.5.7)
Installed from:    SuSE RPMs
OS:                Linux

I tried to import a google ical calender file into Korganizer and I noticed that it fails to display the times correctly. The ical file itself has two timezones: The one where I used to live (GMT +1) and the one I am living now (GMT+7). The second one is not displayed correctly, but is 6 hours off. When I import the same ical file in Mozilla Sunbird it does display correctly. I guess korganizer does not know how to handle two timezones in a ical file. I looked inside the ical file and I see these two entries at the top:

 X-WR-TIMEZONE:Asia/Phnom_Penh
BEGIN:VTIMEZONE
TZID:Europe/Amsterdam
X-LIC-LOCATION:Europe/Amsterdam
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
DTSTART:19700329T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
DTSTART:19701025T030000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VTIMEZONE
TZID:Asia/Phnom_Penh
X-LIC-LOCATION:Asia/Phnom_Penh
BEGIN:STANDARD
TZOFFSETFROM:+0700
TZOFFSETTO:+0700
TZNAME:ICT
DTSTART:19700101T000000
END:STANDARD
END:VTIMEZONE

Then this entry is displayed correctly (and is created by Korganizer). My timezone is set to Asia/Phnom_Penh, meaning that this entry is displayed at 19.00 + 7 hours = 0200  
BEGIN:VEVENT
DTSTAMP:20071101T084145Z
ORGANIZER;CN=Bart Geesink:MAILTO:bart@geesink.org
CREATED:20071101T084121Z
UID:KOrganizer-1401005612.541
SEQUENCE:1
LAST-MODIFIED:20071101T084144Z
SUMMARY:test2
DTSTART:20071115T190000Z
DTEND:20071115T210000Z
TRANSP:OPAQUE
END:VEVENT

This one is not (created by google calender). It will be displayed 7 hours too late, meaning it does not recognize that it is planned in my own timezone.
BEGIN:VEVENT
DTSTART;TZID=Asia/Phnom_Penh:20071106T100000
DTEND;TZID=Asia/Phnom_Penh:20071106T130000
DTSTAMP:20071101T084425Z
UID:6lgr85ntjqfmqmp7p81c0tbh84@google.com
CLASS:PRIVATE
CREATED:20071101T084334Z
LAST-MODIFIED:20071101T084334Z
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:test3
TRANSP:OPAQUE
END:VEVENT

Comment 1 Bart Geesink 2008-01-23 08:23:31 UTC

The problem is not occuring anymore. I think the google calender format was the culprit. Closing the bug now, since no-one confirmed.

Comment 2 Wolfgang Binder 2008-02-02 12:59:39 UTC

I notice a similar problem: icals and text-parts have diffent time. The text-part has right time, ical-field shows same appointment one hour later. Imported icals have wrong time about 1 hour as a result. The ical/vcal-source seems to show right time - time-zone interpreded in a wrong manner?