I think the problem with the vcal is that I stripped the time off of all-day 
events. Without a time the client appears to assume “T000000Z”, which is 
midnight UTC. For me that would be 5 PM local time the previous day, which is 
when the event shows up on my calendar. Adding T000000 to the DTSTART should 
fix the problem.

I expect a similar problem exists with ical exports for people living west of 
SLC * as we are effectively stating the event starts at midnight Mountain time, 
which is still the previous day for people to the west. For ical I should 
probably not put the timezone info for all day events and I should in those 
cases use the VALUE=DATE parameter to avoid associating a time with the event.

Poking around I also found the reason why the ical file doesn’t import into 
outlook * it needed the DTSTAMP field. That will be an easy fix.

pete



_____________________________________________
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 08, 2006 6:59 AM
To: "LDS Open Source Software" <ldsoss@lists.ldsoss.org>
Subject: Re: [Ldsoss] Stake/Ward Web Site Utilities



Jeff Raymond wrote:
> I can verify the Outlook 2003 bug with events that don’t have an
> assigned time. They import as the day before the actual event.

Yes, there is a problem with "all day" events with the vcal export. The
problem shows up in Apple iCal as well when I import the calendar as a
vcal file.

Pete,

It looks like you are missing the "RRULE" line.   For an all day event I
had to do something like:

        BEGIN:VEVENT
        SUMMARY:General Conference
        DTSTART:20041003T050000Z
        RRULE:D1 20041003T050000Z
        END:VEVENT

I think if you add the RRULE it will fix the problem.

-stacey.
_______________________________________________
Ldsoss mailing list
Ldsoss@lists.ldsoss.org
http://lists.ldsoss.org/mailman/listinfo/ldsoss


------------------------------------------------------------------------------

 
NOTICE: This email message is for the sole use of the
 intended recipient(s) and may contain confidential and
 privileged information. Any unauthorized review, use,
 disclosure or distribution is prohibited. If you are not the
 intended recipient, please contact the sender by reply email
 and destroy all copies of the original message.

------------------------------------------------------------------------------

_______________________________________________
Ldsoss mailing list
Ldsoss@lists.ldsoss.org
http://lists.ldsoss.org/mailman/listinfo/ldsoss

Reply via email to