[Vobject] no TZ info in parsed dates?

Florian Dorn florian.dorn at gmail.com
Thu Jun 18 04:52:43 CDT 2009


I'm having a similar problem to the original one (timezone is not
parsed) with event coming from evolution reading via evolution-python
http://www.conduit-project.org/wiki/evolution-python , namely that
evolution does not add the VTimezone field. What do you suggest, is it
"ok" to just add it and set it to the value of DTSTART;TZID in case
VTIMEZONE is missing?

Just as a side note, the time zone is not ignored with evetns having  RRULE

These are the Events that I'm trying to parse

BEGIN:VCALENDAR
VERSION:2.0
BEGIN:VEVENT
UID:20090618T092712Z-8269-1000-1-68 at flocki-laptop
DTSTAMP:20090618T092712Z
DTSTART;TZID=/softwarestudio.org/Tzfile/Europe/Vienna:20090619T113000
DTEND;TZID=/softwarestudio.org/Tzfile/Europe/Vienna:20090619T120000
TRANSP:OPAQUE
SEQUENCE:6
SUMMARY:11:30 normal (Wien)
CLASS:PUBLIC
CREATED:20090618T093516
LAST-MODIFIED:20090618T093516
BEGIN:VALARM
X-EVOLUTION-ALARM-UID:20090618T093516Z-22629-1000-1-6 at flocki-laptop
DESCRIPTION:11:30 normal (Wien)
ACTION:DISPLAY
TRIGGER;VALUE=DURATION;RELATED=START:-PT15M
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:20090618T093607Z-8269-1000-1-80 at flocki-laptop
DTSTAMP:20090618T093607Z
DTSTART;TZID=/softwarestudio.org/Tzfile/Europe/Vienna:20090619T130000
DTEND;TZID=/softwarestudio.org/Tzfile/Europe/Vienna:20090619T133000
TRANSP:OPAQUE
SEQUENCE:2
SUMMARY:(13:00) REC
CLASS:PUBLIC
RRULE:FREQ=WEEKLY;COUNT=26;INTERVAL=1;BYDAY=FR
CREATED:20090618T093634
LAST-MODIFIED:20090618T093634
BEGIN:VALARM
X-EVOLUTION-ALARM-UID:20090618T093634Z-22629-1000-1-109 at flocki-laptop
DESCRIPTION:(13:00) REC
ACTION:DISPLAY
TRIGGER;VALUE=DURATION;RELATED=START:-PT15M
END:VALARM
END:VCALENDAR


On Wed, Jun 10, 2009 at 17:59, Bill Janssen<janssen at parc.com> wrote:
> Looks like it's updated fairly regularly.
>
> Bill
> _______________________________________________
> VObject mailing list
> VObject at lists.skyhouseconsulting.com
> http://lists.skyhouseconsulting.com/mailman/listinfo/vobject
>


More information about the VObject mailing list