On 20 May 2010 10:34, Ævar Arnfjörð Bjarmason <avarab@xxxxxxxxx> wrote: > On Thu, May 20, 2010 at 07:26, Matthias Moeller > <matthias.moeller@xxxxxxxxxxxxxxxxxxx> wrote: >> I have been searching the web for help and found lengthy discussions >> which state that this is a common problem of the HFS+ filesystem. >> What I did not find was a solution to this problem. Is there a solution >> to this problem? > > Is this problem particular to Git, or do you also get it if you > e.g. rsync from the Linux box to the Mac OS X box? > >> # "U\314\210bersicht.xls" > > You probably have to configure your shell on OSX to render UTF-8 > correctly. It's just showing the raw escaped byte sequence instead of > a character there. > > There isn't anything wrong with OSX in this case, filename encoding on > any POSIX system is only done by convention. You'll find that you have > similar problems on Linux if you encode filename in Big5 or > UTF-32. > > Linux will happily accept it, but your shell / other applications will > render it as unknown goo because they expect UTF-8. Except that isnt a normalized utf8 representation of capital U umlaut, code point U+00DC, (utf8 c3,9c), instead presumably it has been decomposed into a captial U followed by a combining character to add in the umlaut, which IMO is pretty weird. As far as i can tell the filename: "Übersicht.xls" Should be stored in utf8 as: "\303\234bersicht.xls" Also minor nit. UTF-32, as it contains nuls for latin-1 chars would be much much worse than utf8 :-) cheers, Yves -- perl -Mre=debug -e "/just|another|perl|hacker/" -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html