Thanks Ryan. It's actually very good news that you were able to get at least one response back with the correct timezone definition. Our code has some pretty well-behaved retry logic in it, so the correct value should get in there eventually.
Regards, Charlie On Mar 2, 2:35 pm, "Ryan Boyd (Google)" <[EMAIL PROTECTED]> wrote: > Thanks Charlie. You're right -- It looks like the VTIMEZONE > definition doesn't take into account the change in daylight savings. > I filed a high priority bug for this issue. > > Unfortunately, it looks like the cause of the offset may actually be > related to your earlier bug report re 'Recurrences intermittently > getting offset (by 1 > hour?)':http://groups.google.com/group/google-calendar-help-dataapi/browse_th... > > I created several events with the recurrence syntax you specified and > one of them actually did have the correct offset. > > We're working hard to improve these problems with recurrence syntax > parsing. Thanks very much for your continued efforts to bring these > issues to our attention. > > Cheers, > > -Ryan > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
