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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000182 Title: indicator-datetime shows all-day events one day too early To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1000182/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
