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 24, 2005, 07:12 UTC
Message-ID
<20051124021231.nrg8448gk8w4owk8@webmail.spamcop.net>
In-Reply-To
<7v1x16y36r.fsf@assigned-by-dhcp.cox.net>
Quoting Junio C Hamano <junkio@cox.net>:
> 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.

Not to argue with you, but it's worth pointing out that git is heavily multiuser software, and interoperability should not be ranked below local configurability.

> 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".

Yes. Then my patch needs to be changed to set encoding to that setting and only if it's present.

-- Regards, Pavel Roskin

Previous: Junio C HamanoNext: Junio C Hamano
Message 6 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.