Git development
 help / color / mirror / Atom feed
From: Marco Costalba <mcostalba@yahoo.it>
To: git@vger.kernel.org
Subject: GIT character codecs
Date: Sat, 12 Nov 2005 04:37:12 -0800 (PST)	[thread overview]
Message-ID: <20051112123712.75182.qmail@web26301.mail.ukl.yahoo.com> (raw)

Hi all,

   this morning I pulled from git repo and tried to look at Junio japanese name with:

      git-diff-tree -p e6bd23911efd0a2bd756c77d9e7ba6576eb739a1

With my big sorry the name was erroneously shown on my box.

I modified qgit to force the use of utf-8 codec instead of the local one, 
in my case ISO-8859-15.

Now I can see Junio name in beautiful japanese characters, and also the 
correct 'Lukas Sandstrom' name.

The problem is now qgit on my local git archives no more correctly 
shows special italian characters.

So here we arrive at the points:

1) If utf8 is the 'only good one' for GIT repos why git-diff-tree uses 
the local codec, in my case ISO-8859-15.

2) If utf8 is not the 'only good one' but the commits are always saved using the
local codec, how is possible to set the correct codec to use after pulling 
from a remote repo with a different codec (in this case public git repo that 
is in utf8).

Thanks
Marco



		
__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com

             reply	other threads:[~2005-11-12 12:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-12 12:37 Marco Costalba [this message]
2005-11-12 22:00 ` GIT character codecs Junio C Hamano
  -- strict thread matches above, loose matches on Subject: below --
2005-11-13  8:14 Marco Costalba
2005-11-13 10:21 ` Junio C Hamano
2005-11-14  4:47   ` Matthias Urlichs
2005-11-13 17:51 ` Linus Torvalds
2005-11-13 20:52 Marco Costalba
2005-11-14  6:31 Marco Costalba
2005-11-14  7:42 ` Matthias Urlichs

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=20051112123712.75182.qmail@web26301.mail.ukl.yahoo.com \
    --to=mcostalba@yahoo.it \
    --cc=git@vger.kernel.org \
    /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