Re: non-ascii filenames issue

From: John Tapsell <johnflux@gmail.com>
Date: Apr 5, 2009, 10:51 UTC
Message-ID: <43d8ce650904050351p72590d52l8861b3901f95201a@mail.gmail.com>
In-Reply-To: <20090405100127.GA12126@home>

2009/4/5 Gregory Petrosyan <gregory.petrosyan@gmail.com>:

Show 16 quoted lines

> On Sun, Apr 05, 2009 at 12:54:28PM +0300, Teemu Likonen wrote:
>> On 2009-04-05 13:36 (+0400), Gregory Petrosyan wrote:
>>
>> > # Changes to be committed:
>> > #   (use "git rm --cached <file>..." to unstage)
>> > #
>> > #  new file:   "\321\204\320\260\320\271\320\273"
>> > #
>> >                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> >                  "файл" should be here instead
>>
>> It can be fixed with command:
>>
>>     git config --global core.quotepath false
>
> Thanks! That works. Does it make sence to set it to "false" by default?

Unfortunately not, because for some absolutely crazy reason, there is no way at all to tell what encoding the string is in. It never occured to anyone that it might actually be useful to be able to read the filename in an unambiguous way. The result is this sort of mess. Just wait until you try to checkout that file on a new filesystem with a different encoding. Or try to checkout that file in Windows. It's like git decided to step backwards 30 years.

John