Using ai1ec version 1.2.5 and 1.3
When adding an ai1ec calendar in Google via URL, all non ASCII chars appears as 2 question marks (2 byte encoding in utf-8).
My website is set up in UTF8 which actually seems to be the standard encoding for content-type text/calendar. Google bug or feature?
In file class-ai1ec-exporter-controller.php
in line 91
just add the charset so that it reads like this:
header( 'Content-type: text/calendar; charset=utf-8' );
I couldn't find some variable which holds the current charset of the website (wordpress). So if your wordpress is not utf8, this can make everything worse. One might consider checking website's html source code for content-type and change the line appropriate.
So mine is
<meta http-equiv="Content-Type" content="UTF-8" />