When you have a very long event name which the ics file puts onto a second line, DAK does not show a space between the content on line 1 and 2 as it should.
Event name should appear on DAK as:
Super long name for an event which goes onto a second line within ics file
Instead it shows as:
Super long name for an eventwhich goes onto a second line within ics file
There is a space at the start of the second line but DAK seems to strip it.
BEGIN:VEVENT
RRULE:FREQ=MONTHLY;UNTIL=20241220T170000Z;INTERVAL=1;BYDAY=3FR
EXDATE;TZID=Pacific Standard Time:20241115T090000
UID:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
SUMMARY:Super long name for an event
which goes onto a second line within ics file
DTSTART;TZID=Pacific Standard Time:20241018T090000
DTEND;TZID=Pacific Standard Time:20241018T093000
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20241115T164458Z
TRANSP:TRANSPARENT
STATUS:CONFIRMED
SEQUENCE:0
LOCATION:
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-MICROSOFT-REQUESTEDATTENDANCEMODE:DEFAULT
X-MICROSOFT-ISRESPONSEREQUESTED:FALSE
END:VEVENT
When you have a very long event name which the ics file puts onto a second line, DAK does not show a space between the content on line 1 and 2 as it should.
Event name should appear on DAK as: Super long name for an event which goes onto a second line within ics file
Instead it shows as: Super long name for an eventwhich goes onto a second line within ics file
There is a space at the start of the second line but DAK seems to strip it.