Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#9 Git: non-UTF8 storage

open
nobody
None
5
2012-08-15
2012-08-15
Burov Dmitry
No

when committing, one is better to call git config --get -z i18n.commitencoding

if non-empty value is returned, then it specifies commit encoding that should be used instead of UTF-8 (probably in {-F file} mode only, not in {-m Message} mode, when cmd.exe charset prevails)

that also probably applies when reading log, blame and such

http://www.kernel.org/pub/software/scm/git/docs/git-config.html#_options
http://www.kernel.org/pub/software/scm/git/docs/git-commit.html#_discussion

Discussion

  • Burov Dmitry
    Burov Dmitry
    2012-08-15

    BTW, Uwe, why u still call AnsiQuotedStr ? after you ensured no doublequote is found inside the string, it is just redundant. Something like QuoteFileName or sime '"' + s '"' expression would be faster.

    Also u removed all information links. If you have some docs folder or wiki, they could be moved there. But as of now thay are just lost.
    If we ever get knocked by MS VC++ quoting convention again, where will one find the clues.

    You may disliek too meny comments, but still they better be preserved somewhere.