Set UTF-8 encoding and remove invalid characters from uids

[lasse-it]

There is a problem, where that if a uid includes a slash, it fails with the error message "HTTPError: 404 Client Error: Not Found for url: https://owncloud/remote.php/dav/calendars/user/calendar/uid" this can be prevented by replacing all slashes, in the uids

[buzz]

@mossroy I'm happy to see people still use this.
But what purpose does it serve as calendar subscriptions are supported by ownCloud/Nextcloud directly?

[mossroy]

@buzz First, thanks a lot for this piece of software.

To sum up, it is really useful for me, as a workaround for nextcloud/server#1497
Calendar subscriptions on owncloud/nextcloud work well for the web client.
But these calendars are not available through the caldav protocol.
So, if your software/devices support direct subscription to webcal calendars (i.e. ical files downloaded through HTTP, considered read-only), you have to manually subscribe to them on each device.
And, it your software/device does not support it, you're stuck. It's the case for my smartphones, with the built-in calendar application of Firefox OS : it only supports caldav protocol.

Exposing all the calendars through caldav ensures your caldav clients always have all your calendars (including subscriptions), even if you add/remove some of them.

NB : I only contributed half of this pull-request, @lasse-it contributed the slashes workaround (which I could not test because I don't have this issue)

made a mistake

[buzz]

Interesting. That makes sense I guess. I solve this by using some app called ICS subscription or similar on Android.

I would merge

• UTF-8 encoding for downloaded ICS files ef4210d
• Replace slashes in uids with valid url charecters 00a2741

But could you remove 662e356 from the PR as it seems to be specific to the lasse-it fork?

[mossroy]

I agree with you to remove 662e356 from the PR. Unfortunately, I did not submit it myself : I suppose @lasse-it needs to do that

[buzz]

Alright. Either this or I'm going to manually merge the two first commits (later)…

[lasse-it]

Okay, I'll try to remove the README @buzz

[lasse-it]

Should be fixed now