On Tue, 2009-08-11 at 11:37 +0100, Lukas Zeller wrote: > Hi Yongsheng, > > "autoenddate" is significant only for vCalendar 1.0 rendering,
"rendering" = "parsing"? > as it > will turn on detecting 23:59:59 as an end-of-day marker and convert it > to 0:00 the next day and when generating vCalendar 1.0, it will > represent all-day-events according to the <autoenddateinclusive> > setting. For iCalendar 2.0, autodate and autoenddate behave the same. mobical.net uses vCalendar 1.0, whereas all other servers we test with use iCalendar 2.0. So we could change the setting without affecting any of the other servers. However, I'm still a bit fuzzy about how autoenddate interacts with the "detect alldays in vCalendar 1.0 (0:00-0:00 or 23:59 localtime)" part of VCALENDAR_INCOMING_SCRIPT. Can someone walk me through the sequence of conversions that happen when applying autoenddate to the mobical.net example DTSTART/END and why MAKEALLDAY() then fails? -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ os-libsynthesis mailing list [email protected] http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
