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

Re: [PATCH] gitk: UTF-8 support

From
PRPavel Roskin <proski@gnu.org>
Date
Nov 28, 2005, 21:55 UTC
Message-ID
<1133214958.27750.8.camel@dv>
In-Reply-To
<7vr7917hq4.fsf@assigned-by-dhcp.cox.net>
On Sun, 2005-11-27 at 16:12 -0800, Junio C Hamano wrote:
Show 6 quoted lines
> The following patch on top of your patch has seen only very
> light testing, but it seems to do the right thing for my
> repository with utf-8 commit messages and another with euc-jp
> commit messages.  For the latter, I needed to do:
> 
> 	$ git-repo-config i18n.commitencoding euc-jp
Thank you!  I'm glad my code was actually useful.

Now we may want to make git recode commit data to the repository encoding. Lots of iconv/glibc/portability fun on the horizon. At very least git should protest if both i18n.commitencoding and the locale encoding are set to different values.

Another issue is support for non-ASCII characters in the filenames.
-- 
Regards,
Pavel Roskin
Previous: Junio C Hamano
Message 8 of 8 in “gitk: UTF-8 support”
  1. gitk: UTF-8 supportPavel Roskin, Nov 23, 2005
  2. Junio C HamanoNov 24, 2005
  3. Paul MackerrasNov 24, 2005
  4. Pavel RoskinNov 24, 2005
  5. Junio C HamanoNov 24, 2005
  6. Pavel RoskinNov 24, 2005
  7. Junio C HamanoNov 28, 2005
  8. Pavel RoskinNov 28, 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.