Hi.
Thank you very much for providing this script, it has helped me out a lot.
I use it with an outlook365 calendar, and apart from the issue below I have not had any problems.
The following .ical entry is not parsed correctly to org-mode. I believe it is due to the event having been planned on one day and then moved afterwards, but I'm not sure.
If any one have an idea how this could be corrected I would greatly appreciate it.
-- .ical file --
BEGIN:VEVENT
UID:040000008200E00074C5B7101A82E00800000000006799AFA449D801000000000000000
01000000066A8A5B520902545A7C52534564AA34B
RECURRENCE-ID;TZID=Romance Standard Time:20230607T090000
SUMMARY:Vagtplanlægning
DTSTART;TZID=Romance Standard Time:20230531T093000
DTEND;TZID=Romance Standard Time:20230531T100000
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20230531T075705Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:12
RECURRENCE-ID is original date
DTSTART and DTEND are correct dates after event have been moved.
-- .org file --
* Vagtplanlægning
:PROPERTIES:
:ID: 040000008200E00074C5B7101A82E00800000000006799AFA449D801000000000000000
:LOCATION: RH-Lokale-9301-biblioteket
:STATUS: CONFIRMED
:ATTENDING: ATTENDING
:ATTENDEES:
:END:
:LOGBOOK:
CLOCK: [2022-07-06 Wed 09:00]--[2022-07-06 Wed 09:30] => 0:00
:END
<2022-07-06 Wed 09:00-09:30 +1m>
Hi.
Thank you very much for providing this script, it has helped me out a lot.
I use it with an outlook365 calendar, and apart from the issue below I have not had any problems.
The following .ical entry is not parsed correctly to org-mode. I believe it is due to the event having been planned on one day and then moved afterwards, but I'm not sure.
If any one have an idea how this could be corrected I would greatly appreciate it.
-- .ical file --
RECURRENCE-ID is original date
DTSTART and DTEND are correct dates after event have been moved.
-- .org file --