From 590aef9932d5e55aca2d9939dbc860763b098c29 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Hugo=20H=C3=B6rnquist?= Date: Sat, 25 Apr 2020 15:06:05 +0200 Subject: Add comments in vcomponent/parse. --- module/vcomponent/parse.scm | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/module/vcomponent/parse.scm b/module/vcomponent/parse.scm index a2f14316..fdae22dc 100644 --- a/module/vcomponent/parse.scm +++ b/module/vcomponent/parse.scm @@ -211,6 +211,11 @@ row ~a column ~a ctx = ~a (not (attr component 'DTEND))) (set! (attr component 'DTEND) (let ((start (attr component 'DTSTART))) + ;; p. 54, 3.6.1 + ;; If DTSTART is a date then it's an all + ;; day event. If DTSTART instead is a + ;; datetime then the event has a length + ;; of 0? (if (date? start) (date+ start (date day: 1)) (datetime+ start (datetime time: (time hour: 1))))))) @@ -348,6 +353,11 @@ row ~a column ~a ctx = ~a ;; components, but they are still the same event. ;; In our case this means exceptions to reccurence rules, which ;; is set up here, and then later handled in rrule-generate. + ;; NOTE These events also share UID, but are diferentiated + ;; by RECURRENCE-ID. As far as I can tell this goes against + ;; the standard. Section 3.8.4.4. + ;; TODO Also make this grouping when reading in a whole + ;; icalendar-file (one with multiple events) (case (length events) [(0) (format (current-error-port) "WARNING: No events in component~%~a~%" -- cgit v1.2.3