11:50 p.m.
On Fri, 2011-10-21 at 14:05 +0200, Thomas Pequet wrote:
Ok I think it is good now.
Le 21/10/2011 11:54, Patrick Ohly a écrit :
> On Wed, 2011-10-19 at 16:03 +0200, Thomas Pequet wrote:
> > OK Patrick now if it is an all day event, the EXDATE will be with
> > ";VALUE=DATE" :)
> You seem to have implemented this so that it *always* is with
> VALUE=DATE. That's not quite what I suggested. For DTSTART with time,
> EXDATE also should have a time. Here's an example for an incorrect (or
> at least undesirable) transformation as it now happens with Memotoo:
>
> BEGIN:VCALENDAR BEGIN:VCALENDAR
> VERSION:2.0 VERSION:2.0
> BEGIN:VEVENT BEGIN:VEVENT
> SUMMARY:recurrence\, daily\, with e SUMMARY:recurrence\, daily\, with e
> xceptions xceptions
> DESCRIPTION:recurrs seven times\, e DESCRIPTION:recurrs seven times\, e
> xcluding (but counting) Friday and xcluding (but counting) Friday and
> Saturday Saturday
> DTEND:20060406T210000 DTEND:20060406T210000
> DTSTART:20060406T203000 DTSTART:20060406T203000
> EXDATE:20060407T203000 | EXDATE:20060407
> EXDATE:20060408T203000 | EXDATE:20060408
Now it fails differently for something else, or I missed the failure
before:
BEGIN:VCALENDAR BEGIN:VCALENDAR
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
SUMMARY:all-day recurrence\, daily\ SUMMARY:all-day recurrence\, daily\
, with exceptions , with exceptions
DESCRIPTION:recurrs seven times\, e DESCRIPTION:recurrs seven times\, e
xcluding (but counting) Friday and xcluding (but counting) Friday and
Saturday Saturday
DTEND;VALUE=DATE:20060407 | DTEND;VALUE=DATE:20060413
DTSTART;VALUE=DATE:20060406 DTSTART;VALUE=DATE:20060406
EXDATE:20060407 <
EXDATE:20060408 <
RRULE:FREQ=DAILY;UNTIL=20060412 <
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
Note that the returned event also covers a week, but without the
exceptions. That not the same.
--
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.