{"thread":{"id":"2205","subject":"gitweb: charset problem","startedAt":"2005-10-24T07:18:39Z","lastAt":"2005-10-24T12:34:57Z","messageCount":2,"participants":["Nico -telmich- Schottelius","Kay Sievers"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"10525","messageId":"20051024071839.GB4608@schottelius.org","threadId":"2205","inReplyTo":null,"subject":"gitweb: charset problem","fromName":"Nico -telmich- Schottelius","fromEmail":"nico-linux-git@schottelius.org","sentAt":"2005-10-24T07:18:39Z","receivedAt":"2005-10-24T07:18:39Z","isPatch":false,"sender":{"key":"nico-linux-git@schottelius.org","avatar":null},"body":"Hello!\n\ngitweb (my $version =           \"247\";) seems to send utf-8 as meta tag encoding\n(<meta http-equiv=\"content-type\" content=\"text/html; charset=utf-8\"/>).\nThe problem is that the name of the user \"HansjOErg\" (OE is the german umlaut)\nis in iso8859-1 in /etc/passwd.\nThis is guessed, but it does not look like utf-8, as it's a one byte encoding:\n\n00007b0: 3031 323a 3130 303a 4861 6e73 6af6 7267  012:100:Hansj.rg\n\nWhat would be the correct way to fix that? Change the username to utf-8?\n(Is this possible without causing problems in other programs?)\nOr tell gitweb that it should convert non-UTF-8 to UTF-8?\n\nBut we also have another problem: Sometimes we have umlauts in the commit messages.\nThose are also displayed incorrectly. When I switch to iso-8859-1 encoding in mozilla,\nthe characters in the username and in the commit message are ok.\n\nGreetings,\n\nNico\n\n-- \nLatest project: cconfig (http://nico.schotteli.us/papers/linux/cconfig/)\nOpen Source nutures open minds and free, creative developers.\n"},{"id":"10531","messageId":"20051024123457.GA30550@vrfy.org","threadId":"2205","inReplyTo":"20051024071839.GB4608@schottelius.org","subject":"Re: gitweb: charset problem","fromName":"Kay Sievers","fromEmail":"kay.sievers@vrfy.org","sentAt":"2005-10-24T12:34:57Z","receivedAt":"2005-10-24T12:34:57Z","isPatch":false,"sender":{"key":"kay.sievers@vrfy.org","avatar":null},"body":"On Mon, Oct 24, 2005 at 09:18:39AM +0200, Nico -telmich- Schottelius wrote:\n> gitweb (my $version =           \"247\";) seems to send utf-8 as meta tag encoding\n> (<meta http-equiv=\"content-type\" content=\"text/html; charset=utf-8\"/>).\n\nYes, that's is intentional, also the http header is overwritten, if the\nwebserver's default is not utf8.\n\n> The problem is that the name of the user \"HansjOErg\" (OE is the german umlaut)\n> is in iso8859-1 in /etc/passwd.\n\nHuh, not sure if it's a good idea to put that into a username,\nnever tried or ever seen that.\n\n> This is guessed, but it does not look like utf-8, as it's a one byte encoding:\n> \n> 00007b0: 3031 323a 3130 303a 4861 6e73 6af6 7267  012:100:Hansj.rg\n\nSure, 0xf6 is the single letter 'ö' (oe) in iso-8859.\n\n> What would be the correct way to fix that? Change the username to utf-8?\n> (Is this possible without causing problems in other programs?)\n> Or tell gitweb that it should convert non-UTF-8 to UTF-8?\n\nDon't know. At best get rid of the non-ascii chars in /etc/passwd\nif you don't want to get in trouble... :)\n\nAll other programs sure, should definitely use utf8.\n\n> But we also have another problem: Sometimes we have umlauts in the commit messages.\n> Those are also displayed incorrectly. When I switch to iso-8859-1 encoding in mozilla,\n> the characters in the username and in the commit message are ok.\n\nutf8 is the one and only sane encoding if you need more than ascii chars.\nJust convert everything to utf8 from your locale to your webserver and\nall that pain will go away immediately. :)\n\nBest,\nKay\n"}]}