Teemu Likonen <tlikonen@xxxxxx> writes: > As a side note/rant: Git tends to show non-Ascii characters in filenames > as \xxx escape sequences. It's not a big problem but surely it's not > very nice to read if (say) half of the word's letters are escaped like > this. I believe Git is mostly used for tracking source codes where > Ascii-only filenames are a common practice. I'm using Git to develop > Finnish spell-checking system (called Voikko) and we have some > non-Ascii filenames in the repo. git-config(1): core.quotepath:: The commands that output paths (e.g. `ls-files`, `diff`), when not given the `-z` option, will quote "unusual" characters in the pathname by enclosing the pathname in a double-quote pair and with backslashes the same way strings in C source code are quoted. If this variable is set to false, the bytes higher than 0x80 are not quoted but output as verbatim. Note that double quote, backslash and control characters are always quoted without `-z` regardless of the setting of this variable. Since 1.5.2.2 (I think), or at least 1.5.3, so you have new enough version of git (git is now at 1.5.5-rc2). -- Jakub Narebski Poland ShadeHawk on #git -- 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
