The real bug about this incident is that if you send a startTime without an endTime as required for a one day all day event, then google returns the representation for a two day all day event. Mark, if you chose not to specialize the one day all day events, how do you decide if you have a real two day event or a wrong one day event?
Philipp On Dec 15, 6:36 pm, Mark Swanson <[EMAIL PROTECTED]> wrote: > >> >From looking at the code, you may wish to try setting tzShift to null > >> DateTime.setTzShift(null). Hopefully that doesnt have other > >> consequences. > > >> Let us know how that works out. > > > It doesn't work. > > I emailed previously saying it did but it does not. GMT+1/Berlin all-day > > events show up in the previous day.It seems you must have the tzShift when > > using a non-GMT timezone because > without it you wind up on the wrong day. > The problem is that you then have the included timezone in the startTime > toString(), which seems to be messing things up on the server side - > and as Phillip pointed out you must not have a timezone for an all-day > event. > > Just to clarify an inconsistency: > > For a one-day all-day event I send only the startTime as per Philipp's > suggestion. Sent to Google: > > 0460 6c 64 2e 63 6f 6d 27 3e 3c 2f 67 64 3a 65 78 74 ld.com'></gd:ext > 0470 65 6e 64 65 64 50 72 6f 70 65 72 74 79 3e 3c 67 endedProperty><g > 0480 64 3a 77 68 65 6e 20 73 74 61 72 74 54 69 6d 65 d:when startTime > 0490 3d 27 32 30 30 36 2d 31 32 2d 32 37 27 3e 3c 2f ='2006-12-27'></ > 04a0 67 64 3a 77 68 65 6e 3e 3c 2f 61 74 6f 6d 3a 65 gd:when></atom:e > 04b0 6e 74 72 79 3e ntry> > > However, what I get back is: > > 0310 53 74 72 69 6e 67 3d 27 27 3e 3c 2f 67 64 3a 77 String=''></gd:w > 0320 68 65 72 65 3e 3c 67 64 3a 77 68 65 6e 20 73 74 here><gd:when st > 0330 61 72 74 54 69 6d 65 3d 27 32 30 30 36 2d 31 32 artTime='2006-12 > 0340 2d 32 37 27 20 65 6e 64 54 69 6d 65 3d 27 32 30 -27' endTime='20 > 0350 30 36 2d 31 32 2d 32 38 27 3e 3c 67 64 3a 72 65 06-12-28'><gd:re > > So, Google is representing one-day all-day events with a startTime AND > an endTime. This actually makes my code easier if I don't have to > special-case the one-day all-day case. > > In practice, sending the endDate for one-day all-day events works fine > if you work around the bug above. > I carefully set all of the required timezones to Berlin, tested, then > set them back to Canada/Eastern, tested, and it works fine. > > 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 -~----------~----~----~----~------~----~------~--~---
