Hi Lane,

Thanks.  I'm glad it is possible.  A question, though, on some level this is
something I would expect to be handled server side.  Is this a Work Around,
or is this a hard and fast rule now and forever: "Never submit a recurrence
without a VTIMEZONE definition."?

I'm off to figure out how to reliably infer the TZ info from our
datasources.

-Brian
On 8/9/07, Lane LiaBraaten (Google) <[EMAIL PROTECTED]> wrote:
>
>
> Hi Brian,
>
> To get the recurring event to obey DST rules you have to include them
> in the recurrence string.  Try this:
>
> String recurrence = "DTSTART;TZID=America/Los_Angeles:20070806T070000\r
> \n"
>    + "DTEND;TZID=America/Los_Angeles:20070806T080000\r\n"
>    + "RRULE:FREQ=WEEKLY;COUNT=65;BYDAY=MO\r\n"
>    + "BEGIN:VTIMEZONE\r\n"
>    + "TZID:America/Los_Angeles\r\n"
>    + "X-LIC-LOCATION:America/Los_Angeles\r\n"
>    + "BEGIN:DAYLIGHT\r\n"
>    + "TZOFFSETFROM:-0800\r\n"
>    + "TZOFFSETTO:-0700\r\n"
>    + "TZNAME:PDT\r\n"
>    + "DTSTART:19700308T020000\r\n"
>    + "RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU\r\n"
>    + "END:DAYLIGHT\r\n"
>    + "BEGIN:STANDARD\r\n"
>    + "TZOFFSETFROM:-0700\r\n"
>    + "TZOFFSETTO:-0800\r\n"
>    + "TZNAME:PST\r\n"
>    + "DTSTART:19701101T020000\r\n"
>    + "RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU\r\n"
>    + "END:STANDARD\r\n"
>    + "END:VTIMEZONE";
>
> Cheers,
> Lane
>
>
> On Aug 9, 10:15 am, "[EMAIL PROTECTED]"
> <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I think I've found a rather serious bug.  I'm using the Java API and
> > created a recurring meeting
> > (RRULE:FREQ=WEEKLY;COUNT=65;BYDAY=MO,TU,WE,TH,FR ) first instance of
> > which was Nov 2006 2pm.
> >
> > I scrolled through, everything looked fine, but I noticed that the
> > instance of the meeting today was for 3pm not 2pm.  Scrolling back in
> > my calendar I noticed that the error first starts on March 11 2007
> > (beginning of DST).
> >
> > "Wow...that's unfortunate.  But no problem...I notice that events have
> > an addTime, I'll just manually calculate the recurrence and add it
> > in."  Unfortunately, that workaround is a no go.  If you have multiple
> > When's only the first is honored, the rest are ignored.
> >
> > Is this a known bug?
> >
> > Is there a workaround people have used?
> >
> > -Brian
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to