[Dev] [README] i18n checkin

[Grant Baillie]

On Sep 16, 2005, at 12:55, Brian Moseley wrote:

> Brian Kirsch wrote:
>
>
>>    b. When I do a 'Generate Data' from the Test menu does my  
>> module work properly? For example, can I share items with non- 
>> ascii values properly, do they import and export as Ical events,  
>> can I send them in an email?
>>
>
> great questions. along those lines, but more generally: when  
> chandler shares via webdav and caldav, does it convert content to  
> utf-8 or send it directly in its native character encoding? is that  
> reported in the charset parameter of the request's content-type  
> header? what about when retrieving data from the sharing server?

[1] It looks to me as if all our .ics files are created as UTF-8.  
Whether that's implied by the icalendar spec, Jeffrey would know. We  
are creating them with 'Content-Type: text/calendar', but no charset.  
That's arguably wrong.

[2] In the case of .xml files, they're heading out with

Content-Type: text/xml; charset="UTF-8"

Since the UTF-8 is re-specified in the XML itself, maybe those should  
be just "application/xml".


[3] There are still issues with non-ascii collection names. It turns  
that Chandler/zanshin don't always do the right thing with non-ASCII  
names. I fixed that in my svn clone, but ran into a different issue  
with (last night's build of) Cosmo. When sharing a calendar called "•  
Wonderful",

PUT /home/demo/%E2%80%A2%20Wonderful/bda82c06-26f1-11da- 
d842-000d9359ec2c.ics HTTP/1.1

gets me a "403 HTTP/1.1 Forbidden" from Cosmo (works on other  
servers, or if I change the collection name to just "Wonderful").

--Grant