Re: Bug: pull --rebase with é in name

From: Jakub Narebski <jnareb@gmail.com>
Date: Mar 5, 2012, 12:36 UTC
Message-ID: <m3aa3vteat.fsf@localhost.localdomain>
In-Reply-To: <20120305115815.GA4550@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:

Show 27 quoted lines

> On Mon, Mar 05, 2012 at 12:42:14PM +0100, René Haber wrote:
> 
> > I'm running git 1.7.9.2 from Fink Project on MacOS X 10.6.
> > The gitconfig in hex is attached.
> 
> Hmm, looks like pretty standard utf8:
> 
>   0000020: 6d65 203d 2052 656e c3a9 2048 6162 6572  me = Ren.. Haber
> 
> and the same thing I used in my tests. I tried repeating the test with
> v1.7.9.2 on OS X (although my test box is 10.7), and couldn't replicate
> it.
> 
> Can you show us the commit that causes the problem, as printed by "git
> cat-file commit $commit | xxd"? I just want to double-check that there
> are no odd bytes there.
> 
> Also, what happens if you do:
> 
>   sh -c '
>     . /sw/lib/git-core/git-sh-setup
>      get_author_ident_from_commit $commit
>   '
> 
> (my theory is that this is the underlying problem in the rebase, and
> should show the bug; by narrowing it down, it should make testing a lot
> simpler).

Hmmm... one place where I have read about this strange "René" -> "Rene'" conversion is when terminal (console) cannot display unicode, and tries to show it using ASCII:

  http://stackoverflow.com/a/9430419/46058

But it should not matter if we are writing to file, isn't it?

-- 
Jakub Narębski