The current implementation causes issues when importing into Proton Calendar, as unescaping colons isn't expected. I'll open a provisional PR and give that branch a test run, however I won't know if removing colon escaping there won't break it somewhere else
As mentioned in #104, reviewing the spec I've found that colons do not get escaped in TEXT property fields
see here
The current implementation causes issues when importing into Proton Calendar, as unescaping colons isn't expected. I'll open a provisional PR and give that branch a test run, however I won't know if removing colon escaping there won't break it somewhere else