Ævar Arnfjörð Bjarmason wrote: > So, my plan of attack is: > > * Add compat/printf from Free, Open or NetBSD. Maybe make > compat/snprintf.c use that while I'm at it. I would prefer to get this fixed in glibc, but of course that has nothing to do with git. > * Use that instead of the GNU libc printf on systems that have glibc. > * Add a configure check for that. > * Revert 107880a > * Get gettext goodness with LC_CTYPE > > Does anyone see a problem with that? The potential issue is that > LC_CTYPE is for: > > "regular expression matching, should be okay, I think (unless http-backend is a problem) > character classification, worked around (see git-compat-util.h) > conversion, I don't know what this means; iconv() is not affected by LC_CTYPE, is it? > case-sensitive comparison, Could be a problem: we use strcasecmp() heavily. > and wide character > functions." no problem. :) > So it might have unintended side-effects. But the only other > workaround I can see is to decree that all consumers of the localized > messages must have a UTF-8 locale. And that is no workaround at all; the problem is still seen with UTF-8 locales, no? -- 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