Shawn has already provided an example of what happens to a UTF8
string on OS X, so I won't provide a duplicate.
On Feb 3, 2007, at 6:50 PM, Junio C Hamano wrote:
I think it is fairly idiotic and obtuse for a filesystem to
treat pathnames anything but a random sequence of bytes that is
slash separated and NUL terminated. I would need a really hard
convincing to buy any path munging on the git side to match
whatever a stupid filesystem does, especially because we do not
live in the ideal Unicode/utf-8 only world.
That's what I was agreeing with. It drives me crazy that HFS+ is
case-insensitive and now does bad things to UTF8 strings. And I
didn't think that doing munging similar to the FS in git is a good
idea for Git in general, but might be useful for a few people like
myself to have. And it wouldn't break anything that isn't already
broken.
Unfortunately my lack of understanding of ICU means I can't actually
get the code to do anything useful, so it's a moot point.
~~ Brian
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html