git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nico -telmich- Schottelius <nico-linux-git@schottelius.org>
To: Kay Sievers <kay.sievers@vrfy.org>,
	Git Mailing List <git@vger.kernel.org>
Cc: Christian Gierke <ch@gierke.de>,
	Peter Portmann <peter.portmann@sygroup.ch>
Subject: gitweb: charset problem
Date: Mon, 24 Oct 2005 09:18:39 +0200	[thread overview]
Message-ID: <20051024071839.GB4608@schottelius.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]

Hello!

gitweb (my $version =           "247";) seems to send utf-8 as meta tag encoding
(<meta http-equiv="content-type" content="text/html; charset=utf-8"/>).
The problem is that the name of the user "HansjOErg" (OE is the german umlaut)
is in iso8859-1 in /etc/passwd.
This is guessed, but it does not look like utf-8, as it's a one byte encoding:

00007b0: 3031 323a 3130 303a 4861 6e73 6af6 7267  012:100:Hansj.rg

What would be the correct way to fix that? Change the username to utf-8?
(Is this possible without causing problems in other programs?)
Or tell gitweb that it should convert non-UTF-8 to UTF-8?

But we also have another problem: Sometimes we have umlauts in the commit messages.
Those are also displayed incorrectly. When I switch to iso-8859-1 encoding in mozilla,
the characters in the username and in the commit message are ok.

Greetings,

Nico

-- 
Latest project: cconfig (http://nico.schotteli.us/papers/linux/cconfig/)
Open Source nutures open minds and free, creative developers.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

             reply	other threads:[~2005-10-24  7:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-24  7:18 Nico -telmich- Schottelius [this message]
2005-10-24 12:34 ` gitweb: charset problem Kay Sievers
2005-10-24 13:56 ` Horst von Brand
2005-10-24 21:55   ` Daniel Barkalow
2005-10-24 22:39     ` Junio C Hamano
2005-10-25 16:01       ` Daniel Barkalow
2005-10-25 17:31         ` Junio C Hamano
2005-10-25 17:44         ` Junio C Hamano

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=20051024071839.GB4608@schottelius.org \
    --to=nico-linux-git@schottelius.org \
    --cc=ch@gierke.de \
    --cc=git@vger.kernel.org \
    --cc=kay.sievers@vrfy.org \
    --cc=peter.portmann@sygroup.ch \
    /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).