Hello--

It appears that the events have reverted back to the:

DTSTART;TZID=Europe/Madrid:20080714T090000
DTEND;TZID=Europe/Madrid:20080714T100000

format.

Is this a permanent change back?

Cheers,
--Alex

On Jul 16, 11:58 am, "Austin (Google)" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Thanks for updating us on the PHP iCalendar and thank you for the work on
> that project.  Regarding the ICS formart, it will remain the way of using
> GMT as the timezone qualifier from now on.
>
> Thanks,
> Austin
>
> On Tue, Jul 15, 2008 at 11:27 PM, Alex King <[EMAIL PROTECTED]> wrote:
>
> > I think I've actually located the bug in the PHP iCalendar code. A
> > global calendar timezone variable is referenced in the extractDateTime
> > function but is never brought into scope so things don't work
> > properly. I'll see about getting a patch back to PHP iCalendar. If
> > anyone else needs this or wants to help review the patch, please let
> > me know. I'll move further discussion to the proper PHP iCalendar
> > online resources.
>
> > Thanks.
>
> > --Alex
>
> > On Jul 15, 9:22 pm, Alex King <[EMAIL PROTECTED]> wrote:
> > > Hi--
>
> > > It appears that this change has "broken" Google Calendar iCalendars in
> > > PHP iCalendar.
>
> > > Perhaps this has really just exposed a bug in PHP iCalendar's event
> > > parsing, but events are now appearing at incorrect times in PHP
> > > iCalendar. I did a (very) brief review of the PHP iCalendar calendar
> > > parsing code:
>
> >http://phpicalendar.cvs.sourceforge.net/phpicalendar/phpicalendar/fun....
> > ..
>
> > > see function extractDateTime() in date_functions.php where the event
> > > times are parsed.
>
> > > Can you confirm that this is a permanent change in the data format? If
> > > so, I'll see about hacking the PHP iCalendar code. If not, I'll wait
> > > until the change is rolled back.
>
> > > Thanks so much!
>
> > > Cheers,
> > > --Alex King
>
> > >http://alexking.org
>
> > > On Jul 15, 11:39 am, "Austin (Google)" <[EMAIL PROTECTED]> wrote:
>
> > > > Hi,
>
> > > > We changed the format of the ics file to return times in GMT times for
> > > > single events.  This change is due to the fact that many older versions
> > of
> > > > outlook with bad timezone definitions were unable to handle times in
> > local
> > > > time properly.
>
> > > > I would recommend using standard timezone libraries like ICU4C or Joda
> > time
> > > > to perform timezone conversions.
>
> > > > Hope that helps,
> > > > Austin
>
> > > > On Fri, Jul 11, 2008 at 1:15 AM, Paco <[EMAIL PROTECTED]>
> > wrote:
>
> > > > > Starting today the ICS file (exporting calendar events) has changed
> > > > > the DTSTART and DTEND for existing events.
>
> > > > > Yesterday, the following was retrieved for an event:
>
> > > > > DTSTART;TZID=Europe/Madrid:20080714T090000
> > > > > DTEND;TZID=Europe/Madrid:20080714T100000
>
> > > > > And now I retrieved the following for the same event:
>
> > > > > DTSTART:20080714T070000Z
> > > > > DTEND:20080714T080000Z
>
> > > > > As you can see there is a difference of 2 hours ( I guess for the
> > > > > timezone).
>
> > > > > How can I get events in the yestarday's format? or is this caused by
> > a
> > > > > temporary error/change in Google?
>
> > > > > In order to circunvent this problem with my application, how can I
> > > > > determine the real time taking in account the timezone and dayligth
> > > > > saving as reported in the ICS file?
>
> > > > > Thanks
> > > > > Paco

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