From: Michael J Gruber <git@drmicha.warpmail.net>
To: "Noralf Trønnes" <notro@tronnes.org>,
"Nico Williams" <nico@cryptonector.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Subject: Re: Git messes up 'ø' character
Date: Thu, 22 Jan 2015 10:59:02 +0100 [thread overview]
Message-ID: <54C0C9E6.50207@drmicha.warpmail.net> (raw)
In-Reply-To: <54BED5FF.40107@tronnes.org>
Noralf Trønnes schrieb am 20.01.2015 um 23:26:
> Den 20.01.2015 23:18, skrev Nico Williams:
>> On Tue, Jan 20, 2015 at 10:38:40PM +0100, Noralf Trønnes wrote:
>>> Yes:
>>> $ echo Noralf Trønnes | xxd
>>> 0000000: 4e6f 7261 6c66 2054 72f8 6e6e 6573 0a Noralf Tr.nnes.
>>>
>>> Is there a command I can run that shows that I'm using ISO-8859-1 ?
>>> I need something to google with, my previous search only gave locale
>>> stuff, which seems fine.
>> The locale(1) command tells you what your locale is set to, but it
>> doesn't say anything about your input method -- it only tells you what
>> your shell and commands started from it expect for input and what they
>> should produce for output.
>>
>> The input method will generally be part of your windowing environment,
>> for which you'll have to search how to check/configure your OS
>> (sometimes it can be set on a per-window basis, sometimes it's a global
>> setting).
>>
>> Even if the windowing environment is set to UTF-8, your terminal
>> emulator might be set to ISO-8859-something, so check the terminal
>> emulator (e.g., rxvt, Terminator, GNOME Terminal, PuTTY, ...).
>
> I use putty which was set to ISO-8859-1. Changing this to UTF-8 gave me
> the correct result:
> $ echo Noralf Trønnes | xxd
> 0000000: 4e6f 7261 6c66 2054 72c3 b86e 6e65 730a Noralf Tr..nnes.
>
> Thank you all for helping me!
>
You can also check the encoding of your config file with
file .git/config
or ":set fileencoding" in vim. ":set fileencoding=utf8" would allow you
to convert it easily.
(This assumes that the file does not mix encodings.)
Michael
prev parent reply other threads:[~2015-01-22 9:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 19:46 Git messes up 'ø' character Noralf Trønnes
2015-01-20 20:07 ` Torsten Bögershausen
2015-01-20 20:17 ` Noralf Trønnes
2015-01-20 20:45 ` Ævar Arnfjörð Bjarmason
2015-01-20 21:05 ` Greg Kroah-Hartman
2015-01-20 21:20 ` Jeff King
2015-01-20 21:27 ` Ævar Arnfjörð Bjarmason
2015-01-20 21:23 ` Noralf Trønnes
2015-01-20 21:26 ` Ævar Arnfjörð Bjarmason
2015-01-20 21:38 ` Noralf Trønnes
2015-01-20 21:57 ` Ævar Arnfjörð Bjarmason
2015-01-20 22:18 ` Nico Williams
2015-01-20 22:26 ` Noralf Trønnes
2015-01-22 9:59 ` Michael J Gruber [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=54C0C9E6.50207@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=nico@cryptonector.com \
--cc=notro@tronnes.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).