[Chandler-dev] Last weeks progress in i18n of Chandler

[Brian Kirsch]

 >>> BTW, due to a bunch of cross-platform issues, it's not so good to 
add  non-ASCII files to svn

Yes, svn is not so great at dealing with non-ascii filenames which is a 
bummer :(

We should however, have at least one test in Chandler that does try to 
load a file (ics for example) with a non-ascii name / file path.

Although this is a total hack, this could be accomplished by renaming a 
file checked out from svn from ascii to non-ascii on testing startup and 
then restoring the original name when the testing completes.

For example "testFile.ics" would be renamed "testFile(ü).ics" for testing.
When testing was complete, "testFile(ü).ics"would be renamed back to 
"testFile.ics".

This would get around the svn problem in the short term until the svn 
team fixes their bug.


-Brian




can be accomplished by

Brian Kirsch -  Cosmo Developer / Chandler Internationalization Engineer
Open Source Applications Foundation
543 Howard St. 5th Floor
San Francisco, CA 94105
http://www.osafoundation.org



Grant Baillie wrote:

>
> On May 22, 2006, at 9:29 , Grant Baillie wrote:
>
>>
>> On May 22, 2006, at 8:36, Markku Mielityinen wrote:
>>
>>> Hi,
>>>
>>> A brief list of things that I have done last week:
>>>
>>> ...
>>>
>>> 4) The filesystem unicode tests in /chandler/parcels/osaf/sharing/ 
>>> tests passed in Windows with '\u00FC' characters in the filenames.  
>>> An interesting observation was that cygwin terminal and svn do not  
>>> support unicode filenames. The terminal showed '?' in place of  
>>> '\u00FC' and the svn was unable to process these files and exitted  
>>> with and error. I will repeat this test in Linux as well.
>>
>>
>> BTW, on the Mac (where UTF-8 is the filesystem encoding), the only  
>> way I could get svn to accept non-ASCII filenames was to do
>>
>> export LANG=en_US.UTF-8
>>
>> in my shell. (The en_US isn't important -- you could choose, for  
>> example, fi instead ;).
>>
>> Otherwise, even a single non-ASCII character filename in a  directory 
>> is enough to disable svn completely (even if that file  isn't in svn).
>
>
> BTW, due to a bunch of cross-platform issues, it's not so good to add  
> non-ASCII files to svn. See:
>
> <http://subversion.tigris.org/issues/show_bug.cgi?id=2464>
>
> with more info in the mailing list thread:
>
> <http://svn.haxx.se/users/archive-2006-04/0841.shtml>
>
> --Grant
>
>
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "chandler-dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/chandler-dev