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

Pedro Melo [off-list ref] writes:

On Jan 17, 2008, at 12:16 AM, Linus Torvalds wrote:

quoted

On Wed, 16 Jan 2008, Pedro Melo wrote:

quoted

The difference I see between us is that if I tell my filesystem that
I want to name my file with a particular string encoded in X, users
using encoding Y will be able to read it correctly. I like my
filesystem to make that work for me.

The difference I see between us is that when I tell you that this is
exactly the same thing as your file *contents*, you don't seem to get
it.

I get that you think its the same thing.

What I don't get is why a user should be forced to know what type of
encoding he and the other users are using on all the layers going down
to the filesystem. If two users on different systems or in different
configurations, choose the same unicode string as the name, why do we
need to make it harder for things to just work out?

If you do the normalization in the right place, things will just work
out.  The file system is not the right place.

I'm willing to accept a file system or other layer that normalizes
encoding of filenames if that makes the end-user life easier,
specially in a tool distributed by nature.

Well, as the issue shows it does not make life for the end-user easier.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum