Re: non-ascii filenames issue
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Apr 6, 2009, 09:12 UTC
- Message-ID
- <alpine.DEB.1.00.0904061109330.10279@pacific.mpi-cbg.de>
- In-Reply-To
- <alpine.DEB.2.00.0904060823400.21376@ds9.cixit.se>
Hi,
On Mon, 6 Apr 2009, Peter Krefting wrote:
> It comes from the Unix tradition, unfortunately, that file names are > just a stream of bytes, instead of a stream of characters mapped to a > byte sequence.
How is that different from .txt not having a defined locale?
Really, please, do not add to the non-information.
Show 6 quoted lines
> Since most people on Linux nowadays probably are running in a > UTF-8-based locale, I tried introducing some (very incomplete) patches > for the Windows port to make this assumption, to allow Windows users to > make use of non-ASCII file names (Windows uses Unicode strings for file > names). Mac OS uses (semi-decomposed) UTF-8 strings, so it should also > be able to make use of this.
Most Russian programmers I know do not run in a UTF-8 locale.
> Unfortunately, there seems to be quite some resistance towards deciding > on a platform- and language-independent way of storing file names in > Git, but rather just going the "Unix" way and making it someone elses > problem. I find this a bit sad.
I find it a bit unfair that you say that, after many people participated in that very informative thread, and after I tried to work with you personally on getting the stuff into 4msysgit.git.
Actually, not just only a bit.
Ciao, Dscho