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

Re: [PATCH] gitk: UTF-8 support

From
Junio C Hamano <junkio@cox.net>
Date
Nov 24, 2005, 06:23 UTC
Message-ID
<7v1x16y36r.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20051123235315.oht0zjidc4ccg8gs@webmail.spamcop.net>
Pavel Roskin <proski@gnu.org> writes:
> Then what would you do to work with a repository using utf-8 if the current
> locale is not utf-8?
Obviously the same way as I did to try things out:
	$ LANG=en_US.utf8 DISPLAY=:0 gitk blah
> Anyway, I see your point.  Not ever git repository uses utf-8.  It is not
> enforced by git.

That is not the point. Point is that I think the user can use LANG and LC_ALL (I suspect LC_CTYPE is what matters) to get what you want, and I suspect hardcoding utf8 robs users the possibility to deal with a repository that uses something else.

And as I suggested in another message (in the died-out thread about gitweb), we could have i18n.commitEncoding in the configuration to help gitk and gitweb. I think that is the same as your "other option".

Previous: Pavel RoskinNext: Pavel Roskin
Message 5 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.