[Tickets #4399] NEW: Broken iCalendar event timezone interoperabilty with Outlook & others

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=4399
-----------------------------------------------------------------------
 Ticket             | 4399
 Created By         | lists-horde at carlthompson.net
 Summary            | Broken iCalendar event timezone interoperabilty with Outlook & others
 Queue              | Horde Framework Packages
 Version            | HEAD
 Type               | Bug
 State              | Unconfirmed
 Priority           | 3. High
 Owners             | 
-----------------------------------------------------------------------


lists-horde at carlthompson.net (2006-09-08 12:51) wrote:

When importing a calendar event into Kronolith (or viewing it in IMP) from
a user in a different timezone Horde does not respect the timezone
specified for the event and erroneously imports or shows the event as if
it were scheduled for local time. Actually, if the sending application
specifies the date / time as UTC (as Horde Kronolith does itself) then
this does not apply and Horde handles it properly. However most
applications do not specify events in that way and Horde does not handle
them properly. The most notable application that does not work properly
with Horde is of course Microsoft Outlook / Exchange.

For example, I work near San Francisco (US/Pacific timezone) but my
employer is based in Atlanta (US/Eastern timezone). If a coworker based in
Atlanta sends me a calendar invite for a conference call that began at 9am
Eastern time Kronolith will import and show it as being 9am Pacific time
which would make me 3 hours late for the call if I rely on it.