Hello, In October of 2006 I logged a bug about recurring events, and made multiple postings to this group about it.
http://code.google.com/p/google-gdata/issues/detail?id=25&can=2&q= I stopped posting examples of RRULEs that Google fails to parse in Decembre 2006. I was under the assumption that these would be addressed shortly. It seems I was wrong. There are several classes of recurring events that are very common. Here's an example: RRULE:FREQ=YEARLY;BYMONTH=5;BYMONTHDAY=3 Google can not parse this. So Google can not support birthdays in this format. Is the recommended best practice to methodically reverse engineer the limitations of Google's RRULE handling and then create complicated RRULE mappings to and from Google? I'd really like to know. Please understand, I'm not trying to be rude or offend anyone at Google. A bug's a bug and all software has bugs. I'm just humbly curious why something so important like a birthday (lots of other use cases) is not supported - and after being raised as an issue 6 months ago no one has considered it a priority to fix. Cheers. -- http://www.ScheduleWorld.com/ Free Google Calendar synchronization with Outlook, Evolution, cell phones, BlackBerry, PalmOS, Exchange, Mozilla, Thunderbird, Pocket PC/Windows Mobile. Also sync tasks, notes and contacts! WebDAV, vfreebusy, RSS, LDAP, iCalendar, iTIP, iMIP support. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
