[GH-ISSUE #226] Can't parse calendar data: Invalid property #221

Closed
opened 2026-02-25 20:31:11 +03:00 by kerem · 2 comments
Owner

Originally created by @a1466d44-d3dc-4c0b-90c7-315b088731d7 on GitHub (Apr 19, 2018).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/226

Hi

I have the issue that people tend to create Outlook calendar entries with CIFS Share Paths to (in our case MS Onenote) documents. (S:\one\random\share\path...)
The target macOS CalDAV Server is unwilling to accept that string in the DESCRIPTION Field

The error message reads:

<?xml version='1.0' encoding='UTF-8'?>
<error xmlns='DAV:'>
  <valid-calendar-data xmlns='urn:ietf:params:xml:ns:caldav'/>
<error-description xmlns='http://twistedmatrix.com/xml_namespace/dav/'><![CDATA[Can't parse calendar data: Invalid property: 'TextValue: '\o' not allowed': DESCRIPTION:Terminserie [CUT]...[/CUT] Besprechungsprotokolle siehe S:\one\random\share\path\Protokolle.one
...

Maybe some kind of (optional) custom regex replace (eg. select Field name, enter sed style rules) would be nice?
Or automated escaping?
Or the possibility to just skip such entries?
Or some other/better idea?

Originally created by @a1466d44-d3dc-4c0b-90c7-315b088731d7 on GitHub (Apr 19, 2018). Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/226 Hi I have the issue that people tend to create Outlook calendar entries with CIFS Share Paths to (in our case MS Onenote) documents. (S:\one\random\share\path\...) The target macOS CalDAV Server is unwilling to accept that string in the DESCRIPTION Field The error message reads: ``` <?xml version='1.0' encoding='UTF-8'?> <error xmlns='DAV:'> <valid-calendar-data xmlns='urn:ietf:params:xml:ns:caldav'/> <error-description xmlns='http://twistedmatrix.com/xml_namespace/dav/'><![CDATA[Can't parse calendar data: Invalid property: 'TextValue: '\o' not allowed': DESCRIPTION:Terminserie [CUT]...[/CUT] Besprechungsprotokolle siehe S:\one\random\share\path\Protokolle.one ... ``` Maybe some kind of (optional) custom regex replace (eg. select Field name, enter sed style rules) would be nice? Or automated escaping? Or the possibility to just skip such entries? Or some other/better idea?
kerem closed this issue 2026-02-25 20:31:11 +03:00
Author
Owner

@aluxnimm commented on GitHub (Apr 19, 2018):

This is a bug in our used library, which doesn't escape single backslashes properly. We will need a workaround and fix it of course.

<!-- gh-comment-id:382690863 --> @aluxnimm commented on GitHub (Apr 19, 2018): This is a bug in our used library, which doesn't escape single backslashes properly. We will need a workaround and fix it of course.
Author
Owner

@aluxnimm commented on GitHub (Apr 29, 2018):

Will be in next release, commit 527526a

<!-- gh-comment-id:385250575 --> @aluxnimm commented on GitHub (Apr 29, 2018): Will be in next release, commit 527526a
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/outlookcaldavsynchronizer#221
No description provided.