Comment 10 for bug 1000182

Revision history for this message
Charles Kerr (charlesk) wrote :

So after testing use cases a bit further it looks like EDS is sees all-day events like this, and the timezone is irrelevant:

> BEGIN:VEVENT
> UID:20121026T095149Z-3681-1000-3631-132@sita
> DTSTAMP:20121026T094847Z
> DTSTART;VALUE=DATE:20121031
> DTEND;VALUE=DATE:20121101
> TRANSP:TRANSPARENT
> SEQUENCE:3
> SUMMARY:Halloween
> CLASS:PUBLIC
> CREATED:20121026T095207Z
> LAST-MODIFIED:20121026T101948Z
> END:VEVENT

Also in non-all-day events, the begin & end times coming from e_cal_client_generate_instances_sync() are already adjusted from the entry's timezone to UTC. So I don't think there's any path where we need look at the ECalComponent's dtstart/dtend times' timezones.