Version: 3.5.5 (using KDE 3.5.5, Kubuntu (edgy) 4:3.5.5-0ubuntu3) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.17-10-generic I've stumbled accross a tzone problem in korganiser in combination with Zimbra 1. In an empty calendar, I create 1 single appointment from 10.00 to 11.00 (am) 2. I open this calendar in Korganiser and the appointment displays right(!) The calendar file is now: BEGIN:VCALENDAR PRODID:Zimbra-Calendar-Provider VERSION:2.0 METHOD:PUBLISH BEGIN:VTIMEZONE TZID:(GMT+01.00) Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna BEGIN:STANDARD DTSTART:16010101T030000 TZOFFSETTO:+0100 TZOFFSETFROM:+0200 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=10;BYDAY=-1SU END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T020000 TZOFFSETTO:+0200 TZOFFSETFROM:+0100 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=3;BYDAY=-1SU END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT UID:6d33da5d-43ea-48ae-ad6b-58c9cd34150c ORGANIZER:MAILTO:martin@zimbra.infrawijs.nl SUMMARY:10-11 DTSTART;TZID="(GMT+01.00) Amsterdam / Berlin / Bern / Rome / Stockholm / Vie nna":20061116T100000 DTEND;TZID="(GMT+01.00) Amsterdam / Berlin / Bern / Rome / Stockholm / Vienn a":20061116T110000 LOCATION: STATUS:CONFIRMED X-MICROSOFT-CDO-BUSYSTATUS:BUSY X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY TRANSP:OPAQUE DTSTAMP:20061115T163212Z SEQUENCE:0 END:VEVENT 3. I change (location of) the item in Korganiser and save 4. When I reload, the item is moved back exactly 1 hour (09.00 - 10.00) in Korganiser, Zimbra still displays is at the right time, showing the new location. The Calendar file is now this: BEGIN:VCALENDAR PRODID:Zimbra-Calendar-Provider VERSION:2.0 METHOD:PUBLISH BEGIN:VTIMEZONE TZID:(GMT+01.00) Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna BEGIN:STANDARD DTSTART:16010101T030000 TZOFFSETTO:+0100 TZOFFSETFROM:+0200 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=10;BYDAY=-1SU END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T020000 TZOFFSETTO:+0200 TZOFFSETFROM:+0100 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=3;BYDAY=-1SU END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT UID:6d33da5d-43ea-48ae-ad6b-58c9cd34150c ORGANIZER:MAILTO:martin@zimbra.infrawijs.nl SUMMARY:10-11 DTSTART:20061116T090000Z DTEND:20061116T100000Z LOCATION:A STATUS:CONFIRMED X-MICROSOFT-CDO-BUSYSTATUS:BUSY X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY TRANSP:OPAQUE DTSTAMP:20061115T163344Z SEQUENCE:1 END:VEVENT END:VCALENDAR 5. Whenever I move the item in konqueror (and save and reload) it will always be displayed one hour early. this is what the Calendar file looks like after moving the appointment 1 hour forward in konqueror (to 10.00 - 11.00) after which it is again displayed an hour early (09.00 - 10.00). BEGIN:VCALENDAR PRODID:Zimbra-Calendar-Provider VERSION:2.0 METHOD:PUBLISH BEGIN:VTIMEZONE TZID:(GMT+01.00) Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna BEGIN:STANDARD DTSTART:16010101T030000 TZOFFSETTO:+0100 TZOFFSETFROM:+0200 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=10;BYDAY=-1SU END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T020000 TZOFFSETTO:+0200 TZOFFSETFROM:+0100 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=3;BYDAY=-1SU END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT UID:6d33da5d-43ea-48ae-ad6b-58c9cd34150c ORGANIZER:MAILTO:martin@zimbra.infrawijs.nl SUMMARY:10-11 DTSTART:20061116T090000Z DTEND:20061116T100000Z LOCATION:A STATUS:CONFIRMED X-MICROSOFT-CDO-BUSYSTATUS:BUSY X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY TRANSP:OPAQUE DTSTAMP:20061115T163522Z SEQUENCE:1 END:VEVENT END:VCALENDAR I have no idea who is violating the vCal standards, I just know that during all the moving around of the appointment Zimbra kept displaying it at the original and right time. Regards, Martin van Es
I have a similar problem. From Zimbra I recieve a ics with more than one VTIMEZONE: BEGIN:VCALENDAR PRODID:Zimbra-Calendar-Provider VERSION:2.0 METHOD:REQUEST BEGIN:VTIMEZONE TZID:(GMT-08.00) Pacific Time (US & Canada) / Tijuana BEGIN:STANDARD DTSTART:16010101T020000 TZOFFSETTO:-0800 TZOFFSETFROM:-0700 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=10;BYDAY=-1SU END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T020000 TZOFFSETTO:-0700 TZOFFSETFROM:-0800 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=4;BYDAY=1SU END:DAYLIGHT END:VTIMEZONE BEGIN:VTIMEZONE TZID:(GMT+01.00) Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna BEGIN:STANDARD DTSTART:16010101T030000 TZOFFSETTO:+0100 TZOFFSETFROM:+0200 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=10;BYDAY=-1SU END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T020000 TZOFFSETTO:+0200 TZOFFSETFROM:+0100 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=3;BYDAY=-1SU END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT DTSTART;TZID="(GMT+01.00) Amsterdam / Berlin / Bern / Rome / Stockholm / Vie nna":20070416T100000 DTEND;TZID="(GMT+01.00) Amsterdam / Berlin / Bern / Rome / Stockholm / Vienn a":20070416T110000 Korganizer schedules the meeting at 18-19, corresponding to the first timezone (US-pacific), although the DTSTART refers to the other timezone. If I remove the top timezone declaration it imports right. If I switch the to declarations it also work. Perhaps libkcal only uses the first VTIMEZONE and ignores TZID ?
tzid support was fixed in kde4.