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

Re: GIT character codecs

From
Matthias Urlichs <smurf@smurf.noris.de>
Date
Nov 14, 2005, 04:47 UTC
Message-ID
<pan.2005.11.14.04.47.25.899163@smurf.noris.de>
In-Reply-To
<7v3bm0c0gf.fsf@assigned-by-dhcp.cox.net>
Hi, Junio C Hamano wrote:
> I suspect you could just take the default from LANG and LC_CTYPE
> to cover 98% of the cases, and to cover the rest 2% the
> problematic cases have a per-window override menu.

Or, if you want to be super-flexible, just try to decode as UTF-8. Success? fine -- otherwise use whatever your application's default is set to, or your local encoding (which may of course also be UTF-8), or fall back to 8859-15.

-- 
Matthias Urlichs   |   {M:U} IT Design @ m-u-it.de   |  smurf@smurf.noris.de
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
 - -
Difficult:
	Disciplines like physics, math, engineering, which is why I don't
	want to do them.
		-- Fashionable Dictionary (www.butterfliesandwheels.com)
Previous: Junio C HamanoNext: Linus Torvalds
Message 3 of 4 in “Re: GIT character codecs”
  1. Marco CostalbaNov 13, 2005
  2. Junio C HamanoNov 13, 2005
  3. Matthias UrlichsNov 14, 2005
  4. Linus TorvaldsNov 13, 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.