Frank Mantek wrote: > The problem though is that the calendar converts single event entries to UTC > time on the server, and returns them to you in the timezone of the calendar > they are in. > > What you want could only be solved by having individual timezone settings > per entry, but we don't have that on the Google Calendar. >
Thanks for the reply. However, it seems to me that this is a *major* failing with Google Calendar, if it doesn't have the ability to associate Events with a time-zone. Just storing a UTC offset is not good-enough. It does not allow identification when (as is the case) several different world time-zones can have same offset. And it completely falls apart when trying to work sensibly with DST (daylight saving time). Users do not wish to be aware of DST, but it must just "work". They don't want to see an Evnet's time appear to change just because their point of observation has moved from Summer Time to Standard Time! John 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 -~----------~----~----~----~------~----~------~--~---
