umlaute in filename
Hi, I'm a subversion client on linux. Recently I encounter errors like this: svn update svn: Error converting entry in directory 'Fein/AP11_Faktura_Sonderaufgaben' to UTF-8 svn: Valid UTF-8 data (hex: 20 53 50 52 49 4e 54 20 20 53 53 54 20 31 31 31 20 2d 20 20 47 72 6f) followed by invalid UTF-8 sequence (hex: df 6b 75 6e) Actually the error message is in German because my locale is usually set to de_DE.UTF-8. For this English mailing list I set it to en_US.utf8. The problem is that the other German windows users checked in files with German umlaute in filenames. How can I solve this problem? I have to mention that all contents od our sources are encoded in utf-8. This is the reason why I set LANG to de_DE.UTF-8. Unfortunately I do not know in which encoding filenames under windows are written and how to change it. Thomas
Re: umlaute in filename
Thank you. A new checkout solved the problem. Thomas Philip Martin hat am 30. Mai 2012 um 11:08 geschrieben: > "tho...@randspringer.de" writes: > > > I'm a subversion client on linux. > > Recently I encounter errors like this: > > > > svn update > > svn: Error converting entry in directory 'Fein/AP11_Faktura_Sonderaufgaben' > > to UTF-8 > > svn: Valid UTF-8 data > > (hex: 20 53 50 52 49 4e 54 20 20 53 53 54 20 31 31 31 20 2d 20 20 47 72 6f) > > followed by invalid UTF-8 sequence > > (hex: df 6b 75 6e) > > > > Actually the error message is in German because my locale is usually set to > > de_DE.UTF-8. > > For this English mailing list I set it to en_US.utf8. > > > > The problem is that the other German windows users checked in files with > > German umlaute in filenames. > > > > How can I solve this problem? I have to mention that all contents od our > > sources are encoded in utf-8. This is > > the reason why I set LANG to de_DE.UTF-8. > > > > Unfortunately I do not know in which encoding filenames under windows are > > written and how to change it. > > I don't think that is a Windows problem. The hex looks like ISO-8859-1: > " SPRINT SST 111 - Großkun" so it appears that you have done a checkout > or update in a non-UTF-8 locale (perhaps de_DE?) and created the > non-UTF-8 path on disk. Then you have switched to a UTF-8 locale and > tried to continue using the working copy. > > One solution is to checkout a new working copy in the UTF-8 locale. > Another is to go back to the non-UTF-8 locale. It may be possible to > convert the existing working copy to UTF-8 by removing the non-ascii > paths and using update/revert to recreate them in UTF-8. > > -- > Philip
