[OGo-Bugs][Bug 1928] Whole day events span two days instead of one in *.ics files
bugs@opengroupware.org
bugs@opengroupware.org
Mon, 21 Apr 2008 10:11:27 +0200 (CEST)
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug
report.
http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=1928
os@xn--ball-epa.net changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Whole day events span two |Whole day events span two
|days instead of one in *.ics|days instead of one in *.ics
|files |files
CC| |os@xn--ball-epa.net
------- Additional Comments From samuli.seppanen@tietoteema.fi 2007-11-30 09:59 -------
>From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; fi-FI; rv:1.8.1.8) Gecko/20071004
Iceweasel/2.0.0.8 (Debian-2.0.0.6+2.0.0.8-0etch1)
Description of problem:
One-day all-day event created in OGo shows up as two-day all-day event in
Zidestore-served iCalendar files.
A screenshot of the event in OGo-webui:
http://www.tietoteema.fi/tmp/ogo-wholeday.jpg
Corresponding iCalendar entry:
BEGIN:VEVENT
LOCATION:Office
STATUS:CONFIRMED
SUMMARY:Whole day event
DTSTART;VALUE=DATE:20071129
DTEND;VALUE=DATE:20071130
TRANSP:OPAQUE
UID:skyrix://ogo.tietoteema.fi/ogo-template.tietoteema.fi/402821
CREATED:20030710T120000Z
DTSTAMP:20071130T081304Z
X-MICROSOFT-CDO-IMPORTANCE:0
X-MICROSOFT-CDO-BUSYSTATUS:BUSY
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-CDO-ALLDAYEVENT:TRUE
ATTENDEE;CUTYPE="INDIVIDUAL";PARTSTAT="NEEDS-ACTION";ROLE="REQ-PARTICIPANT";RSVP="FALSE";CN="Samuli
Seppänen":MAILTO:removed_intentionally
ORGANIZER;CN="Samuli Seppänen":MAILTO:removed_intentionally
END:VEVENT
END:VCALENDAR
DTEND value should be 20071129 instead of 20071130 because this event does not
span two days but one.
The error has been verified with Mozilla Firefox and by syncing OGo with Nokia
phones and Outlook. The error causes Outlook and Nokia S60 phone calendars to
see this event as a two-day event.
The relevant sections in RFC2445 (http://www.ietf.org/rfc/rfc2445.txt)
* 4.3.4: Date
* 4.3.5: Date-Time
* 4.6.1: Event component
are not especially clear on whether to create whole-day events. Whether
Opengroupware.org should use the DATE or DATE-TIME type for whole-day events
depends on a couple of factors:
* A national holiday like Christmas Eve should definitely use the DATE-type,
because Christmas Eve's absolute DTSTART and DTEND values depend on the
Timezone. In effect Christmas Eve starts at 00:00 no matter which timezone
you're in.
* If, for example, someone is unavailable for one whole day, it's better to
use DATE-TIME. That way people would know when that person becomes available, no
matter what timezone they're in.
* Events that span several days, like vacation on the Caribbean should
probably be defined with the DATE-TIME-type for the same reason as above.
Version-Release number of selected component (if applicable):
ogo-zidestore-1.1.7-r1987.0
How reproducible:
Always
Steps to Reproduce:
1. Create an all-day event in OGo-webui
2. Load the corresponding calendar.ics file from Zidestore
3. Compare the start- and endtimes in webui and the ics file
Actual Results: One-day all-day event in OGo webui shows up as two-day all-day
event in Zidestore-served calendar.ics files
Expected Results: One-day all-day event should be one-day all-day event even in
Zidestore
Additional info:
------- Additional Comments From os@xn--ball-epa.net 2008-04-21 10:11 -------
Hello,
I just reported a bug that seems to be related to this one. All-day events
exported by Zidestore are missing the last day in KOrganizer. See
http://bugs.kde.org/show_bug.cgi?id=158801
KOrganizer interprets the DTSTART/DTEND values correctly (as it appears to me),
but if the X-MICROSOFT-CDO-ALLDAYEVENT:TRUE line is present, it removes one day
at the end such that events spanning only one day disappear completely!
To me as an end-user it appears that the only problem is in the Microsoft
extension (because KOrganizer and OpenGroupware seem to share the same notion of
when an all-day-event begins and ends), but I guess it is more complex than
that. I have to admit that at this point, I begin to be slightly confused about
what the correct iCal syntax is.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.