1

D:\Temp\autohotkey-efficiency>git mergetool 鼠标配合.ahk Merging: "\351\274\240\346\240\207\351\205\215\345\220\210.ahk"

"\351\274\240\346\240\207\351\205\215\345\220\210.ahk": file not found Continue merging other unresolved paths (y/n) ?

I do have 鼠标配合.ahk at this location.

Is git capable of handling international characters or do I have to change any settings?

Update:

Setting core.quotepath to false doesn't work.

D:\Temp\autohotkey-efficiency>git config --global core.quotepath false

D:\Temp\autohotkey-efficiency>git mergetool 鼠标配合.ahk Merging: "\351\274\240\346\240\207\351\205\215\345\220\210.ahk"

"\351\274\240\346\240\207\351\205\215\345\220\210.ahk": file not found Continue merging other unresolved paths (y/n) ?

Gqqnbig
  • 5,845
  • 10
  • 45
  • 86

1 Answers1

2
git config --global core.quotepath false

Reference: how to handle asian characters in file names in git on os x

Community
  • 1
  • 1
ElpieKay
  • 27,194
  • 6
  • 32
  • 53
  • It doesn't work however. See my update. Did I miss anything? – Gqqnbig Jun 29 '16 at 07:02
  • @LoveRight `git config -e` to check if there is `[core] quotepath` and what its value is. – ElpieKay Jun 29 '16 at 07:17
  • There is [core] section, but no quotepath. I manually added it in. Now the error is `榧犳爣閰嶅悎.ahk: file not found`. The characters are wrong probably related to encoding. – Gqqnbig Jun 30 '16 at 03:08
  • @LoveRight since the global config would be overwritten by the local config, I was afraid that the local config had core.quotepath as true. I tried it both in Ubuntu and Windows, git version v2.8, merge tool kdiff3 and vimdiff. With core.quotepath false, cmd like `git log --name-only` outputs the file in its real name. If not false, it's like \351\274. – ElpieKay Jun 30 '16 at 03:11
  • @LoveRight that's most probably the key. My locale encoding is utf-8. – ElpieKay Jun 30 '16 at 03:18