ForumsQuestionsEncode of Live Cal Link
Encode of Live Cal Link
| Author | Message |
|---|---|
|
eiryu.t |
I am using ToodleDo in the language of Japan.
I am having it display in the Google calendar by using Live iCal Link. However, the display of the character is amusing. I think that there is a problem in the encode of Live iCal Link. Perhaps, I think that the cause is a thing that UTF-8 is not specified for encode. Is this problem improved? |
|
unisyn |
I have the same issue.
When using the Live iCal link in Gcal, 2byte characters appear 'bugged' due to some sort of encoding issue. I work around this by using only English as my todo-language, but would be nice if it became multi-byte compliant. |
|
Jake Toodledo Founder |
Yes, this is a known bug that we have been looking into. Actually, we think it is a bug with Google not accepting UTF-8 characters in an iCal link. If you try importing the iCal link into Apple's iCal program, the characters will come across just fine, so something is funny with Google. They are notorious for having poor iCal support.
|
|
unisyn |
Hi, thank you for the feedback.
I did some more research on my own and got it to work! Seems that Gcal needs text encoding specified explicitly within the Content-type header. So I proxied the live iCal link at my personal webserver ... and changed it's Content-type header; and fed it to Gcal. Toodledo's current header: Content-Type: text/calendar New header, altered by script: Content-Type: text/calendar; charset=utf-8 Voila! No more corrupt multi bytes :) Some additional notes... - Also seems to require Content-Length (didn't work when omitted) - Doesn't work when "Transfer-Encoding: chunked" is On |
|
Jake Toodledo Founder |
Hey, thanks for the help. We'll put this in our side and see if that fixes it.
|
|
eiryu.t |
Thank you for the comment.
The reference: In the Google calendar of Japan, the following iCal is correctly displayed. webcal://ical.mac.com/ical/Japanese32Holidays.ics |
|
Ana Rita |
Have you managed to work around this bug with unysin's solution? I'm still getting garbled text on my gcal subscription.
|
|
Jake Toodledo Founder |
Still working on it.
|
|
Jake Toodledo Founder |
Just an update. We tried to add utf-8 to the content-type, but Google still corrupts the multi-byte characters. You must have done something else to get it to work. We're still looking into it.
|
|
unisyn |
Hi, here are my server's HTTP headers for your reference.
GET /MYICSFILE HTTP/1.1 Host: MYICSSERVER User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.11) Gecko/2009060215 Firefox/3.0.11 (.NET CLR 3.5.30729) Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive HTTP/1.x 200 OK X-Powered-By: PHP/5.2.6-2ubuntu4.2 Content-Type: text/calendar; charset=utf-8 Transfer-Encoding: wambo Content-Length: 5573 Date: Thu, 18 Jun 2009 05:06:26 GMT Server: lighttpd/1.4.19 I have the feeling, that maybe, the lack of GZIP compression is making the difference (Toodledo's ICS link is gzip compressed) JFYI |
|
Jake Toodledo Founder |
Thanks for the tip. We'll investigate.
|
You cannot reply yet
U Back to topic home
R Post a reply
To participate in these forums, you must be signed in.