Re: Weird filename encoding issue
- From
Jakub Narebski <jnareb@gmail.com>
- Date
- Oct 17, 2008, 08:57 UTC
- Message-ID
- <m3hc7bk39g.fsf@localhost.localdomain>
- In-Reply-To
- <c6c947f60810170108q3038b66bj2ad89bdcb7105903@mail.gmail.com>
"Alexander Gladysh" <agladysh@gmail.com> writes:
Show 19 quoted lines
> Steps to reproduce: > > 1. Create git repo on Windows machine, add there file, named > "Копия.txt" (Russian for Copy.txt) in CP1251 (NOT UTF-8). Just in > case, hopefully correctly named file is attached. > > File must be added and committed from git gui, not from command line. > > $ mkdir test && cd test > $ git init > <put file there> > $ git gui > > 2. Share the repo somewhere, so it would be accessible from OS X (repo > should still be on Windows machine). > > 3. Clone repo to OS X machine and see the weird behaviour. Git status > can't decide how file should be named, "%CA%EE%EF%E8%FF.txt" or > "\312\356\357\350\377.txt".
I _suspect_ that it is caused by known issue with MacOS X filesystem in default settings. Git assumes that what he puts in filesystem is the same that it reads from filesystem; there is ongoing (although bit stalled) effort to make Git work around this. Unfortunately HFS+ does not, I think, fullfil this requirement.
-- Jakub Narebski Poland ShadeHawk on #git