From: "Shawn O. Pearce" <spearce@spearce.org>
To: "Uwe Kleine-König" <ukleinek@informatik.uni-freiburg.de>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [BUG] git gui and my ö
Date: Tue, 24 Apr 2007 01:39:35 -0400 [thread overview]
Message-ID: <20070424053935.GO17480@spearce.org> (raw)
In-Reply-To: <20070423113225.GA5427@lala>
Uwe Kleine-K??nig <ukleinek@informatik.uni-freiburg.de> wrote:
> commit-tree failed:
>
> <sha1 sum>
> Warning: commit message does not conform to UTF-8.
> You may ...
>
> The commit was done with git-commit, I have
>
> zeisberg@cassiopeia:~$ set | grep -E '^L(ANG|C_)'
> LANG=en_US.UTF-8
> LC_CTYPE=en_US.UTF-8
What does your git-config think is the value of i18n.commitencoding?
If its unset git-gui assumes utf-8 as the encoding. Hmm...
This particular code is around line 1287 of git-gui:
1287 # -- Build the message.
1288 #
1289 set msg_p [gitdir COMMIT_EDITMSG]
1290 set msg_wt [open $msg_p w]
1291 if {[catch {set enc $repo_config(i18n.commitencoding)}]} {
1292 set enc utf-8
1293 }
1294 fconfigure $msg_wt -encoding $enc -translation binary
1295 puts -nonewline $msg_wt $msg
1296 close $msg_wt
We should be writing the commit message (here $msg) out to a
temporary file ($msg_p / $msg_t), using a UTF-8 encoding ($enc).
Apparently that's not what's happening here. I wonder if the Tk
text widget is feeding me UTF-8, and the way I have configured the
file channel Tcl is than mangling things futher... *sigh*
Anyone reading this a better Tcl guru than I?
I'll try to take a look at this tomorrow. I'll have to figure out
how to get your proper name into git-gui first. :-)
I had thought I had most of git-gui i8n safe, but apparently not.
Thanks for the bug report!
--
Shawn.
next prev parent reply other threads:[~2007-04-24 5:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-23 11:32 [BUG] git gui and my ö Uwe Kleine-König
2007-04-24 5:39 ` Shawn O. Pearce [this message]
2007-04-24 6:16 ` Shawn O. Pearce
2007-04-24 8:57 ` Uwe Kleine-König
-- strict thread matches above, loose matches on Subject: below --
2007-04-25 22:48 Brett Schwarz
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=20070424053935.GO17480@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=ukleinek@informatik.uni-freiburg.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.