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 <kay.sievers@vrfy.org> 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. :) > 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. Kay - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Tue May 31 20:45:13 2005
This archive was generated by hypermail 2.1.8 : 2005-05-31 20:45:14 EST