[Dev] [README] i18n checkin

[Brian Kirsch]

Brian Kirsch - Email Framework Engineer
Open Source Applications Foundation
543 Howard St. 5th Floor
San Francisco, CA 94105
(415) 946-3056
http://www.osafoundation.org



Brian Moseley wrote:

> Grant Baillie wrote:
>
>> [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.
>
>
> i think icalendar specifies the default charset of an icalendar object 
> as utf-8 but allows the encapsulating mime message to use the 
> content-type header's charset param to specify an alternate charset 
> which was used to generate property and parameter values.
>
> seems like chandler could either normalize localized data into utf-8 
> when constructing icalendar objects (difficult)

Since textual data in Chandler is stored as unicode encoding to utf-8 
should not prove difficult. Chandler converts from native charsets to 
Unicode at I/O boundaries and all keyboard input from the user is also 
unicode.



> or use the localized data as is and report the charset when 
> transporting the icalendar objects.
>
>> [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".
>
>
> what document specifies the meaning of 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").
>
>
> this is likely bug 3068 
> (<https://bugzilla.osafoundation.org/show_bug.cgi?id=3068>). webdav 
> collection and resource names are used directly as item names in the 
> repository, and many characters are not allowed in item names. there 
> is an open bug with jackrabbit to url-escape names before using them 
> as repository item names. this will hopefully be fixed in the cosmo 
> 0.3 timeframe.
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/dev