Re: Cyrillic VC Git commit messages

[Eli Zaretskii]

> From: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
> Date: Fri, 21 Nov 2014 17:38:51 +0300
> 
> > Could you give a pointer to that place?
> 
> It's mentioned here.  
> <https://github.com/msysgit/msysgit/wiki/Git-for-Windows-Unicode-Support#Disable_commit_message_transcoding>
>   Couldn't find a more elaborate explanation.

I see nothing there that says it's a feature.  I don't even see there
a confirmation that output is always in UTF-8.  Can you tell how you
decided that, or where did you see that described?

Do I understand correctly that you see Cyrillic text encoded
differently when it is sent to Emacs and to the cmd.exe window?  And
it sends codepage 1252 (not 1251) to the cmd.exe window?

Moreover, you seem to say that Git outputs in UTF-8 even though you
customized i18n.logoutputencoding to be windows-1251?  That'd be a
real bug in Git.  How about asking about that on the msysgit mailing
list?

This message:

  http://osdir.com/ml/msysgit/2009-11/msg00140.html

seems to say that the problem disappears if you use --no-pager, so
maybe the bug is in Less?  There are some suggestions to play with the
value of the environment variable LESSCHARSET.

(This information might be obsolete with the current versions of
msysgit.)

> VC does is not using process-coding-system-alist at all. 
> vc-git-commits-coding-system is used instead.

That's not true.  First, vc-git-commits-coding-system is used only in
2 commands in vc-git; others use process-coding-system-alist.  More
importantly, even those 2 commands bind only one of the coding
systems, the other is determined by process-coding-system-alist.

Not sure this helps you, though.

Anyway, if nothing else works for you, modify vc-git.el to use 2
variables instead of just one for input and output of logs, then you
can give each variable the value you need.