After set i18n.commitencoding = utf-8,The Log still commit in ANSI(GBK) In Windows

2,222 views
Skip to first unread message

KingLiang Gu

unread,
Aug 21, 2011, 8:57:43 AM8/21/11
to msy...@googlegroups.com
Just as what the title tells,And see http://code.google.com/p/msysgit/issues/detail?id=557
when I set  i18n.commitencoding = utf-8, The Log still commit in ANSI(GBK) In Windows,Which cause the log display as Garbled character in Linux git Client/TortiseGit。

This is the message mSYSGit gives me。

Warning: commit message does not conform to UTF-8.
You may want to amend it after fixing the message, or set the config
variable i18n.commitencoding to the encoding your project uses.



 

ihipop

unread,
Aug 22, 2011, 2:15:36 AM8/22/11
to msysGit
http://code.google.com/p/msysgit/issues/detail?id=557
This is the correct URI

On 8月21日, 下午8时57分, KingLiang Gu <ihi...@gmail.com> wrote:
> Just as what the title tells,And seehttp://code.google.com/p/msysgit/issues/detail?id=557

Johannes Sixt

unread,
Dec 1, 2012, 10:07:53 AM12/1/12
to pimpo...@gmail.com, msy...@googlegroups.com
Am 01.12.2012 11:07, schrieb pimpo...@gmail.com:
> You can write this in command line:
> git config --global i18n.commitencondig UTF-8
>
> This is working for me.

Perhaps you are misunderstanding the purpose of the configuration. It
does *not* mean

"I want the commit message to be encoded in xyz."

It rather means

"The text that I feed as commit message is encoded in xyz."

Therefore, I think that the correct setting would be

git config i18n.commitencoding cp936

When you change your editor to produce UTF-8 commit messages, then you
would have to adjust this configuration accordingly.
-- Hannes

Reply all
Reply to author
Forward
0 new messages