From: David Woodhouse <dwmw2@infradead.org>
To: Martin Koegler <mkoegler@auto.tuwien.ac.at>
Cc: git@vger.kernel.org, Jakub Narebski <jnareb@gmail.com>,
Junio C Hamano <junkio@cox.net>
Subject: Re: gitweb - encoding problems
Date: Mon, 21 May 2007 20:33:32 -0400 [thread overview]
Message-ID: <1179794012.2771.112.camel@shinybook.infradead.org> (raw)
In-Reply-To: <20070521205721.GA21771@auto.tuwien.ac.at>
On Mon, 2007-05-21 at 22:57 +0200, Martin Koegler wrote:
> I use ISO-8859-1 as my locale, so my blobs, commits and tags are in
> this encoding.
That's a very strange thing for anyone to do in the 21st century.
Did you configure this archaic thing correctly in .git/config?
Otherwise, gitweb will assume that you're using utf-8 like any normal
person would, and of course you'll have problems when it tries to deal
with your legacy character set as if it were something sensible.
--
dwmw2
next prev parent reply other threads:[~2007-05-22 0:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 20:57 gitweb - encoding problems Martin Koegler
2007-05-21 21:09 ` Ismail Dönmez
2007-05-22 0:33 ` David Woodhouse [this message]
2007-05-22 7:50 ` Jakub Narebski
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=1179794012.2771.112.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=junkio@cox.net \
--cc=mkoegler@auto.tuwien.ac.at \
/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).