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

Re: [KORG] Encoding problem with the git documentation

From
HAH. Peter Anvin <hpa@zytor.com>
Date
Jul 22, 2007, 18:07 UTC
Message-ID
<46A39CEA.7020703@zytor.com>
In-Reply-To
<20070722174915.GI26471@cip.informatik.uni-erlangen.de>
Alexander Wuerstlein wrote:
Show 10 quoted lines
> 
> There are 2 resolutions for this problem, changing the charset the webserver
> delivers in the response headers or recoding the html to be utf-8. One
> possibility to fix the response headers would be to use the 'AddDefaultCharset'
> directive (http://httpd.apache.org/docs/2.2/de/mod/core.html#adddefaultcharset)
> like 'AddDefaultCharset Off' or 'AddDefaultCharset ISO-8859-1'.
> This could also be set in .htaccess, so the persons responsible for the subtree
> can control the charset by themselves without your interaction. Of course
> the right solution depends on your setup which you know best about :)
>

We're aware of this problem, and the first answer is the right one -- this is 2007 and UTF-8 is what we should use everywhere.

However, the second option (using .htaccess) is available.
	-hpa
Next: Linus Torvalds
Message 1 of 4 in “Re: [KORG] Encoding problem with the git documentation”
  1. H. Peter AnvinJul 22, 2007
  2. [KORG] gitweb down?Linus Torvalds, Jul 22, 2007
  3. Never mind (Re: [KORG] gitweb down?)Linus Torvalds, Jul 22, 2007
  4. H. Peter AnvinJul 22, 2007

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.