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

Re: GIT character codecs

From
MCMarco Costalba <mcostalba@yahoo.it>
Date
Nov 14, 2005, 06:31 UTC
Message-ID
<20051114063126.27817.qmail@web26306.mail.ukl.yahoo.com>
Matthias Urlichs wrote:
Show 12 quoted lines
>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.
>
How it is possible to test for success?

The codec could see everything decodable, but It's only from the context, i.e. the user who reads, that it is possible to realize it's the wrong codec.

Anyhow, as I posted previous in this thread, qgit-0.97.2 now has a codec selector
 as a persistent setting, defaulting to local codec.
  Marco
		
__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com
Next: Matthias Urlichs
Message 1 of 2 in “Re: GIT character codecs”
  1. Marco CostalbaNov 14, 2005
  2. Matthias UrlichsNov 14, 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.