On Thu, 17 Jan 2008, Pedro Melo wrote:
On Jan 17, 2008, at 6:09 PM, Mark Junker wrote:
quoted
IMHO it would be the best solution when git stores all string meta data in
UTF-8 and converts it to the target systems file system encoding. That would
fix all those problems with different locales and file system encodings ...
+1.
And I would suggest the use of RFC 3454 as the guidelines for UTF-8
normalization.
The problem is that there is no way to know what the "target system
encoding" is.
And it wouldn't actually solve the bigger problem on OS X anyway: as long
as you are case-insensitive, you'll have all the same problems (ie the
insane OS X filesystem presumably thinks that "MÄRCHEN" and "Märchen" are
also identical, because they are "equivalent" names).
Linus