Hi again, Ãvar ArnfjÃrà Bjarmason wrote: > While that's not a perfect solution I think it's the best we're going > to get for the time being. I'm pretty convinced that if I tried to > make git itself LC_CTYPE-safe as part of this already huge series it'd > never get merged. Having messages with question marks from strerror() > on certain platforms is an OK compromise in my opinion. The question marks[1] are what I was referring to. Consider this from the point of view of someone working on the Debian package: would users consider that an appropriate or positive change for squeeze+1? (Hint: not if it doesn't come with some benefit in their locale, no.) I suspect making git work with other LC_CTYPE would not actually be too hard[2]. Such fixes are useful for futureproofing and increased sanity anyway --- they do not have to be part of the l10n branch imho. [1] fatal: unable to stat 'foo.c': Op?ration non permise [2] except that annoying printf bug. -- 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