> You mean we should do the same thing as Apple with HFS? Are you serious? Yes, I'm serious. IMHO there should be a defined clear encoding used for files names in the repository. Otherwise you don't know what you can expect by reading it - it could mean anything. File names are in fact strings which are based on characters. To convert characters to bytes (or visa versa) you need to know the encoding. -- Best regards, Thomas Singer ============= syntevo GmbH http://www.syntevo.com http://blog.syntevo.com Johannes Schindelin wrote: > Hi, > > On Thu, 26 Nov 2009, Thomas Singer wrote: > >> [someone said, Thomas did not say who] >> >>> But as you said, this still doesn't make the Apple normal form any >>> easier. Though if we know we are on such a strange filesystem we >>> might be able to assume the paths in the repository are equally >>> damaged. Or not. >> Well, if the git-core folks could standardize on, e.g., composed UTF-8 >> (rather then just UTF-8), for storing file names in the repository, then >> everything should be clear, isn't it? > > You mean we should do the same thing as Apple with HFS? Are you serious? > > Ciao, > Dscho -- 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