Hey there,
I just imported my calendar into nozbe, and noticed that all my events were shifted forward 6 hours after importing it into ical – the same as my time zone difference. After ensuring my time zones were set correctly everywhere else (nozbe, my mac, etc)
Digging into a sample event exhibiting this problem I found:
(irrelevant fields removed)
BEGIN:VEVENT
DTSTAMP:20100629T202205Z
DESCRIPTION:Call from Erik at apple (D 1 Jul 13:30) (T 1 h) (@ Waiting-for)
DTEND;TZID=UTC;20100701T213000
DTSTART;TZID=UTC;20100701T203000
SUMMARY:Call from Erik at apple
END:VEVENT
in this example, DTEnd and DTStart are not in proper ical format – if I change them to the proper format they work correctly, and the time is now in my current zone:
DTEND;TZID=UTC;VALUE=DATE-TIME:V20100701T213000
DTSTART;TZID=UTC;VALUE=DATE-TIME:20100701T203000
...
I have a perl script that can scrub the malformed output into the correct output, but it would be nice if you would fix this on your end.
Note that events that are ‘All Day’ seem to be output correctly, it is only the ones that include a time that seem to be output in a hosed fashion.
Thanks! Nick
Comments:
Thx for this. I will post it to our tech.
Any news on this issue? Nick’s suggestion seems quite relevant and convincing.
Alfonso
This problem still seem to persist – I missed an appointment yesterday because I looked at my iCal instead of Nozbe website :(
Any ETA on resolving it?
I’m surprised it still continues. I will repost to our tech… but I rather see it as a returning matter then continuation of the old. Regardless, it needs to be solved.
The relevant RFC: http://www.ietf.org/rfc/rfc2445.txt
A slightly simpler way to properly format these two lines according to the RFC would be:
DTEND:V20100701T213000Z
DTSTART:20100701T203000Z
(note the trailing capital Z)