From: Tobias Getzner <tobias.getzner@gmx.de>
To: git@vger.kernel.org
Subject: Re: [BUG] Mojibake in git gui and gitk for certain unicode chars
Date: Thu, 22 Jan 2015 13:18:22 +0100 [thread overview]
Message-ID: <1421929102.22955.3.camel@gmx.de> (raw)
In-Reply-To: <1421927001.11296.27.camel@gmx.de>
On Do, 2015-01-22 at 12:43 +0100, Tobias Getzner wrote:
> Hello,
>
> I’ve noticed git gui and gitk seem to have problems decoding certain
> unicode characters. E.g., when a commit contains the character «👍»
> (thumbs up sign; U+1F44D) in UTF-8 encoding, this character will show
> as «ð» in gitk.
> I’ve noticed a perhaps related glitch when the options in git gui is
> shown. My committer name contains the character «ß» (latin small letter
> sharp s; U+00DF). The text field in the options dialog displays this as
> «Ã»,
I suppose that some of the mojibake characters in the message might
have been stripped out of the message because they are control chars.
So, «👍» was rendered as «ð\x9f\x91\x8d». «ß» was rendered as «Ã\x9f».
prev parent reply other threads:[~2015-01-22 12:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 11:43 [BUG] Mojibake in git gui and gitk for certain unicode chars Tobias Getzner
2015-01-22 12:18 ` Tobias Getzner [this message]
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=1421929102.22955.3.camel@gmx.de \
--to=tobias.getzner@gmx.de \
--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;
as well as URLs for NNTP newsgroup(s).