Re: git on MacOSX and files with decomposed utf-8 file names

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jan 17, 2008, 00:57 UTC
Message-ID: <alpine.LSU.1.00.0801170054280.17650@racer.site>
In-Reply-To: <16C3D0BC-3A70-441C-89D9-71B5F0DA0790@simplicidade.org>

Hi,

On Thu, 17 Jan 2008, Pedro Melo wrote:

Show 14 quoted lines

> On Jan 17, 2008, at 12:33 AM, Johannes Schindelin wrote:
> 
> > On Wed, 16 Jan 2008, Linus Torvalds wrote:
> > 
> > > So if you are a case-insensitive filesystem, then normalization is 
> > > sane.
> > 
> > Actually, no.  Even an case-challenged filesystem should keep the 
> > _original_ name around, if only for the exact same argument you used 
> > earlier: if the user chooses to capitalise some letters, but not 
> > others, it is not the filesystem's place to "correct" that.
> 
> For the record, HFS+ is case-insensitive but case-preserving so I 
> believe they keep the original filename around.

For the record, that's only the default setting. AFAIK you can configure it to care about case, too.

Also for the record, the whole thread was about HFS+ _not_ keeping the original filename around, but _only_ a normalised version of it.

> But I think that focusing on HFS+ is loosing sight of the real problem. 
> It's not about encoding at the filesystem, but encoding inside the git 
> structures.

So far I have not seen anyone talking _seriously_ about this issue. Only a few shouts "you should support", and a few shouts back "I don't care about insane filesystems".

Therefore, I fully agree with you that we're losing sight of the real problem.

Ciao, Dscho