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

GIT character codecs

From
MCMarco Costalba <mcostalba@yahoo.it>
Date
Nov 12, 2005, 12:37 UTC
Message-ID
<20051112123712.75182.qmail@web26301.mail.ukl.yahoo.com>
Hi all,
   this morning I pulled from git repo and tried to look at Junio japanese name with:
      git-diff-tree -p e6bd23911efd0a2bd756c77d9e7ba6576eb739a1
With my big sorry the name was erroneously shown on my box.

I modified qgit to force the use of utf-8 codec instead of the local one, in my case ISO-8859-15.

Now I can see Junio name in beautiful japanese characters, and also the correct 'Lukas Sandstrom' name.

The problem is now qgit on my local git archives no more correctly shows special italian characters.

So here we arrive at the points:
1) If utf8 is the 'only good one' for GIT repos why git-diff-tree uses 
the local codec, in my case ISO-8859-15.
2) If utf8 is not the 'only good one' but the commits are always saved using the
local codec, how is possible to set the correct codec to use after pulling 
from a remote repo with a different codec (in this case public git repo that 
is in utf8).

Thanks Marco

		
__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com
Next: Junio C Hamano
Message 1 of 2 in “GIT character codecs”
  1. Marco CostalbaNov 12, 2005
  2. Junio C HamanoNov 12, 2005

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.