From: Kay Sievers Date: Tue, 31 May 2005 12:21:30 GMT Subject: Re: [gitweb PATCH] Configure encoding Message-ID: <20050531122130.GA24395@vrfy.org> In-Reply-To: <11399.1117537956@www67.gmx.net> On Tue, May 31, 2005 at 01:12:36PM +0200, Thomas Kolejka wrote: > > --- Ursprüngliche Nachricht --- > > Von: Kay Sievers > > An: Petr Baudis > > Kopie: Thomas Kolejka , Git Mailing List > > > > Betreff: Re: [gitweb PATCH] Configure encoding > > Datum: Tue, 31 May 2005 12:44:25 +0200 > > > > On Tue, May 31, 2005 at 12:12:17PM +0200, Petr Baudis wrote: > > > Dear diary, on Tue, May 31, 2005 at 11:19:55AM CEST, I got a letter > > > where Kay Sievers told me that... > > > > On Tue, May 31, 2005 at 09:55:11AM +0200, Thomas Kolejka wrote: > > > > > The following patch makes it easy to change the encoding: > > > > > > > > > > > > > > > --- gitweb.cgi.177 2005-05-31 09:43:17.000000000 +0200 > > > > > +++ gitweb.cgi.p 2005-05-31 09:48:46.000000000 +0200 > > > > > @@ -20,6 +20,9 @@ > > > > > my $my_uri = $cgi->url(-absolute => 1); > > > > > my $rss_link = ""; > > > > > > > > > > +my $encoding = "utf-8"; > > > > > +$encoding = "iso-8859-1"; > > > > > > > > The upstream version will not support anything but the one and only > > > > sane encoding which is utf-8. It will not provide options to switch > > > > back to the 80's, sorry. :) > > > > > > This matters mainly for commits, right? > > > > Yes. Also the content of the files, but fortunately they are just plain > > ascii most of the time. :) > > I've made this changes becausae the german letters like ä, ö, ... are > displayed ugly in the browser. So use a sane encoding in your commit-text. We don't store the encoding with the commit, so you don't have any sane other option besides using utf-8 if you don't use plain ascii. > > > Perhaps I should recode from current locale to utf8 in cg-commit? > > > > Everthing else than utf-8 is just a complete mess with data shared > > across multiple machines. All modern distributions defaulting to utf-8 > > anyway, so I think it is sane to recode that utf-8. > > The patch is to _change_ the encoding easy .. or to leave it unchanged. Exactly. Change to other encodings is not supported upstream and will not be a configuration value, sorry. Kay