quoted
If `i18n.filenameslocalencoding' option was set via git-config to a
correct <codepage> encoding, 2 things should be done:
Windows supports UTF-16 file names, but need to use wchar_t APIs for fopen()
and friends. Have you looked at any of that?
No, I didn't look towards Windows handling of Unicode, because Git under
Windows works well enough without that: I've built Git in MinGW/MSYS
environmment (using the patches we're discussing) and it handles
cyrillic filenames in Windows ANSI CP1251 codepage just as was planned:
writes filenames to tree objects in UTF-8, checks out them into working
dir in CP1251, other stuff as git-clone, git-diff, git-status, etc also
works ok. One remaining issue (offtopic here, as far as I understand) to
make TortoiseGit work with UTF-8 Git's output.
--
\\// Peter - http://www.softwolves.pp.se/
--
Timur Sufiev