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

Re: gitweb: charset problem

From
Daniel Barkalow <barkalow@iabervon.org>
Date
Oct 24, 2005, 21:55 UTC
Message-ID
<Pine.LNX.4.64.0510241743280.25300@iabervon.org>
In-Reply-To
<200510241356.j9ODuAHn005060@laptop11.inf.utfsm.cl>
On Mon, 24 Oct 2005, Horst von Brand wrote:
Show 7 quoted lines
> > But we also have another problem: Sometimes we have umlauts in the commit
> > messages.  Those are also displayed incorrectly. When I switch to
> > iso-8859-1 encoding in mozilla, the characters in the username and in the
> > commit message are ok.
> 
> I believe the Emperor Penguin decreed messages have to be ASCII, or else
> UTF-8. Please don't add to the mess by using non-portable encodings!
Should we possibly reject non-UTF-8 input to commits?

IIRC, we actually define that to be UTF-8, unlike most of the other stuff, for which we don't actually insist on a policy.

	-Daniel
*This .sig left intentionally blank*
Previous: Horst von BrandNext: Junio C Hamano
Message 2 of 6 in “Re: gitweb: charset problem”
  1. Horst von BrandOct 24, 2005
  2. Daniel BarkalowOct 24, 2005
  3. Junio C HamanoOct 24, 2005
  4. Daniel BarkalowOct 25, 2005
  5. Junio C HamanoOct 25, 2005
  6. Junio C HamanoOct 25, 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.