From: Kay Sievers <kay.sievers@vrfy.org>
To: Petr Baudis <pasky@ucw.cz>
Cc: Thomas Kolejka <Thomas.Kolejka@gmx.at>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [gitweb PATCH] Configure encoding
Date: Tue, 31 May 2005 12:44:25 +0200 [thread overview]
Message-ID: <20050531104425.GA23755@vrfy.org> (raw)
In-Reply-To: <20050531101217.GA25555@pasky.ji.cz>
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
next prev parent reply other threads:[~2005-05-31 10:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 7:55 [gitweb PATCH] Configure encoding Thomas Kolejka
2005-05-31 9:19 ` Kay Sievers
2005-05-31 10:12 ` Petr Baudis
2005-05-31 10:44 ` Kay Sievers [this message]
2005-05-31 11:12 ` Thomas Kolejka
2005-05-31 12:21 ` Kay Sievers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050531104425.GA23755@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=Thomas.Kolejka@gmx.at \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).