Hello Even though the KB says it's the client's fault, we have come to believe that there is a timezone issue with the ICS feed. It seems the VTIMEZONE definition from the ICS does not take the DST changes into account, at least partially.
I also noticed that some EXDATE's contain foreign timezone definitions (namely /mozilla.org/20050126_1/America/New_York) which, so it seems, Google didn't process during the import. The foreign timezones are not included in the ICS feed, which violates rfc2445. Therefore, the error described in the first comment of [1] shows up in sunbird/lightning. A solution would be to either add the timezone definitions from the imported calendar, or to upgrade the event to a Google native timezone. Please read the comments (especially the last ones, comment #9) on [1] I suggest this is high priority, since the timezone changes are already in effect since the beginning of march. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=365812 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
