Robin Rosenberg <robin.rosenberg.lists@xxxxxxxxxx> writes: > I can't talk about "most" here, only local conditions, i.e. northern Europe > where both the legacy ISO encodings are very common with a steady increase in > UTF-8 usage, in the Linux community. People using OSS in windows almost > exclusively get the windows-1252 (for most practical purposes the same as > ISO-8859-1). > > Even a *very* small set of random people you will wind up with people having > different locales. More problematic is the case where pathnames and contents are in different encodings, even for the same language. For example, my mbox files that store messages I receive from people in Japan have contents in ISO-2022 as that is the longstanding standard encoding used for e-mail over there, but the pathname encoding used by the system I have that mbox file on is EUC-JP. If I were to create a patch between two versions of such a file, the diff header would show the pathname encoded in one, and the changed contents would ben shown in another. As long as you treat "git diff" output as binary blob, that would work just fine, but when you have to transmit such a diff in e-mail as an in-line patch, you would have troubles. - 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
