Re: [Evolution] Time drifting using Android - Exchange 2010 - Evolution




Den 05/31/2013 10:56 AM, skrev David Woodhouse:
Remember, times are meaningless without timezones. You should *always*
specify the timezone unless it's completely obvious.

The meeting was at 20:00 in *what* time zone? I thought it was at 20:00
in your local time zone, GMT+2. Which makes it 18:00 GMT?
Sorry about that! The meeting was at 20:00 GMT+2
They're base64-encoded. Here's the first one, which I think is the
interesting one:
Correct: this was entered on my phone as a meeting at 20:00 GMT+2
BEGIN:VCALENDAR
METHOD:PUBLISH
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T030000
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T020000
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Vidar Seeberg:MAILTO:vidar seeberg norsvin no
SUMMARY;LANGUAGE=en-US:Test entered for 20-21
DTSTART;TZID=W. Europe Standard Time:20130602T200000
DTEND;TZID=W. Europe Standard Time:20130602T210000
UID:1fe056fd367849478ebb324bd2fb0260
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20130531T064042Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2111176071
X-MICROSOFT-CDO-BUSYSTATUS:BUSY
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR

Milan reports the issue being fixed "accidently" in the up and coming 3.8.3. I will try that as soon I get hold of it

Thank you for good explanations and help. I will report back as soon as I have tested 3.8.3

Regards
Vidar


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]