git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Bug: UTF-16, UCS-4 and non-existing encodings for git log result in incorrect behavior

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Nov 12, 2008, 14:22 UTC
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:
Show 8 quoted lines
> 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

Previous: Constantine PlotnikovNext: Johannes Schindelin
Message 2 of 6 in “Bug: UTF-16, UCS-4 and non-existing encodings for git log result in incorrect behavior”
  1. Constantine PlotnikovNov 12, 2008
  2. Johannes SchindelinNov 12, 2008
  3. Johannes SchindelinNov 12, 2008
  4. Alexander GavrilovNov 12, 2008
  5. Johannes SchindelinNov 12, 2008
  6. Alexander GavrilovNov 12, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.