On Jan 27, 8:06 pm, Ray Baxter <[email protected]> wrote: > You might search through the archives for some previous posts on this subject. > > The problem is that the notion of all-day events means two distinct > things and Google can't know which one you mean: > > 1) The Fourth of July is an all-day event the runs from > 2009-07-04T00:00:00 to 2009-07-05T00:00:00 in every time zone of the > world. > > 2) The 24 hours of the Fourth in New York City runs from > 2009-07-04T00:00:00-05:00:00 to 2009-07-05T00:00:00-05:00, which is > different in every time zone. > > The mixing of conventions leads to the results that you are seeing.
Ah, that does make some sense. However, the calendar has a timezone associated with it that it uses for every other event, and when looking at graphical displays of the calendar, it knows to put all-day events on the correct day (and not at a weird hour offset). Is there a way to specify that I want the all-day events to be in the same time zone as the normal events? I tried using the czt parameter, and specifying the start-min and start-max with a timezone, and neither seemed to work. It seems to me that the confusion stems from that timezone issue, but the actual bug could be fixed. When would anyone want to see all-day events for UTC when they are looking at a local calendar? Thanks! - Jeff --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
