From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Wed, 12 Nov 2008 14:22:46 GMT
Subject: Re: Bug: UTF-16, UCS-4 and non-existing encodings for git log result in incorrect behavior
Message-ID: <alpine.DEB.1.00.0811121521390.30769@pacific.mpi-cbg.de>
In-Reply-To: <85647ef50811120532h778769ddx69f0b111dbad359a@mail.gmail.com>

Hi,

On Wed, 12 Nov 2008, Constantine Plotnikov wrote:

> If UTF-16[BE|LE] or UCS-4[BE|LE] encodings are used with git log, the 
> git completes successfully but commit messages and author information 
> are not shown. I suggest that git should fail with fatal error if such 
> zero producing encoding is used.
> 
> If the incorrect encoding name is used, the git log does not perform any 
> re-encoding, but just display commits in their native encoding. I 
> suggest that git should fail with fatal error in this case as well.

Have you set the correct encoding with i18n.commitEncoding?  If not, you 
should not be surprised: Git's default encoding is UTF-8, and that fact is 
well documented, AFAICT.

Ciao,
Dscho