path: root/AUTHORS
diff options
authorLars Henriksen <LarsHenriksen@get2net.dk>2020-05-02 22:14:45 +0200
committerLukas Fleischer <lfleischer@calcurse.org>2020-05-03 08:59:01 -0400
commitfabacecd16eb62ff94dfa8955862852a410e3524 (patch)
tree88780b27d17adfe53214300c8b17ddde0588715e /AUTHORS
parent8fffc9dc8e5dd930785ef00e58000e5b1b2afd25 (diff)
Take value data type of event start into account in iCal import/export
The patch derives the item type (appointment or event) from the DTSTART value type. It is then used to perform an extended check of date/time values and reject non-conformant import files (like those reported in Github issues #81, (calcurse) events. The patch includes parsing and code corrections and minor refactoring. Background: Ical events are of two types, in calcurse called appointments and events. RFC 5545 has no distinguishing names for them, but describes them in section 3.6.1. The event type is derived from the value type of the DTSTART property. The value type may be either DATE-TIME (appointment) or DATE (event). If not specified by a VALUE property parameter in DTSTART, the default value type is DATE-TIME. The value type must be set explicitly to DATE to get an event. Other properties and rrule parts must agree with the DTSTART value type (DTEND, DURATION, EXDATE and UNTIL). Previously the type of an imported event was derived from the format of the DTSTART value. The DTSTART value type was not taken into account when importing, and not specified for recurring events when exporting (commit 0114289 solved it for events, see GitHub PR #97). Signed-off-by: Lukas Fleischer <lfleischer@calcurse.org>
Diffstat (limited to 'AUTHORS')
0 files changed, 0 insertions, 0 deletions