Exporting my Calendar as iCal file and importing this file in Windows Calendar, all events have changed their time from "GMZ +1" to "UTC" (that's what Windows Calendar says).
Is it possible, to tell EssentialPIM always to use "GMT +1" during export and to write that into the file .csv?
Does EssentialPIM export no time zones?
Re: Does EssentialPIM export no time zones?
I found the reason (there is no VTIMEZONE section in the file exported with EssentialPIM).
So I have to copy the time zone information into the .csv file, and then it works! Alle events are correct imported in Windows Calendar (which I use to synchronize my EssentialPIM calendar with my S40 mobile phone).
Example:
BEGIN:VTIMEZONE
TZID:Amsterdam\, Berlin\, Bern\, Rom\, Stockholm\, Wien
BEGIN:STANDARD
DTSTART:20001029T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:Mitteleuropäische Zeit
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:Mitteleuropäische Sommerzeit
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
So I have to copy the time zone information into the .csv file, and then it works! Alle events are correct imported in Windows Calendar (which I use to synchronize my EssentialPIM calendar with my S40 mobile phone).
Example:
BEGIN:VTIMEZONE
TZID:Amsterdam\, Berlin\, Bern\, Rom\, Stockholm\, Wien
BEGIN:STANDARD
DTSTART:20001029T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:Mitteleuropäische Zeit
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:Mitteleuropäische Sommerzeit
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
-
- Site Admin
- Posts: 21714
- Joined: Wed Dec 08, 2004 11:39 pm
- Has thanked: 819 times
- Been thanked: 364 times
- Contact:
Re: Does EssentialPIM export no time zones?
Hi,
thank you!
Well, we save time in UTC format in iCal. That's an universal time and as far as I can see from iCal specification, timezones in this case are not needed. The problem is, Windows Calendar, does not understand the UTC part of specification, while EPIM does not understand the timezone part:(
thank you!
Well, we save time in UTC format in iCal. That's an universal time and as far as I can see from iCal specification, timezones in this case are not needed. The problem is, Windows Calendar, does not understand the UTC part of specification, while EPIM does not understand the timezone part:(
Maxim,
EPIM Team
EPIM Team