The calendar team is aware of that issue, but i am unaware currently if there is a resolution on this. I will forward and come back to you on that.

With the event organisation this makes sense. You know though, that, at least using the API, you can fix this yourself? Would that help for now?

The way to fix this (drumroll):

-> use an extendedProperty to store the local eventtimezone offset
-> use a webContent property for the event to display the local time

That should work

Frank Mantek

On 10/11/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:


Frank Mantek wrote:

>
> Major failing depends on user base and usage pattern. For me, as i travel a
> bit, you might be correct.
>

I am managing events organised around the world, by an international
corporation. Although most delegates will only travel within their owo
continent, many do travel all over the world. And even more will
certainly travel from east to west coast USA (we have recently
organised events in San Francisco, Chicago and Virgina). So the
delegates do want to see the times as they will be when then arrive,
not as viewed from where they currently are. And web / PC based
calendar systems are often used as a starting point for loading an
event and agenda into a PDA, smart-phone or ordinary cellphone
calendar, where it is essential that times are "local".

>
> This is not an easy feature to implement in a manner that it does not hurt
> usability for the default case (beside engineering costs).
>

I agree that not many applications handle this fully, but most do at
least retain all the timezone information for the event. The
application that handles timezones very well is Lotus Notes 7. When
displaying an event that is not in the timezone of the "viewer", it
displays:

"This meeting occurs in a different time zone"

A button is beside this message, and when clicked it displays (e.g.):

"Meeting is in time zone (GMT+10:00) Brisbane
Here    Wednesday 15:00 - Thursday 15:00
There   Thursday 00:00 - Friday 00:00"

A very nice solution IMHO.

Q: Is there any way that this whole timezone issue can be raised as a
formal improvement request please? Without it being supported I cannot
see Google Calendar competing with existing calendaring systems.

John H. Walton



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Google Calendar Data API" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/google-calendar-help-dataapi
-~----------~----~----~----~------~----~------~--~---

Reply via email to