From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Niko Dzhus <primenico@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [Bug report] Git incorrectly selects language in macos
Date: Fri, 14 Sep 2018 23:57:22 +0200 [thread overview]
Message-ID: <87a7ojlp31.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <CAKd-JgStGb4Ka9Rs6G2e4ADQKZVrsJMsNGz1sRP_4Ej4=FtxtA@mail.gmail.com>
On Fri, Sep 14 2018, Niko Dzhus wrote:
> It doesn't use English when other language is available as a secondary language.
>
> Reproducing:
>
> 1. Open "Language & Region" in macos settings
> 2. In "Preferred languages" box, set English as a primary language.
> 3. Add another language, that git is translated to, as a secondary
> language, for example, French or German.
> 4. Run any git command - git will use the secondary language, instead
> of English.
>
> When the secondary language is removed, then git starts using English again.
>
> I have git 2.19.0, installed from brew, and my OS is macOS 10.13.6 .
What's the output of these two commands for you:
1. locale
2. env | grep -e LC -e LANG
We don't do any such magic ourselves, so whatever this is is down to how
i18n in general works on your system, do you have any other translated
command-line program that works differently?
I suspect there's some DWYM logic here that always treats English as a
secondary language.
Do you also e.g. get the same results if you select say Swedish as a
primary language and German as a secondary? I.e. a Git in German, as
opposed to Swedish?
next prev parent reply other threads:[~2018-09-14 21:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 19:08 [Bug report] Git incorrectly selects language in macos Niko Dzhus
2018-09-14 21:57 ` Ævar Arnfjörð Bjarmason [this message]
2018-09-15 0:51 ` Niko Dzhus
2018-09-15 2:20 ` Niko Dzhus
2018-09-16 7:15 ` Eric Sunshine
2019-01-15 15:35 ` Nate Weaver
2019-01-15 16:43 ` Nate Weaver
2019-01-15 19:06 ` Nate Weaver
2019-01-15 20:36 ` Eric Sunshine
2019-01-16 2:16 ` Jonathan Nieder
2019-01-16 2:28 ` Jonathan Nieder
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=87a7ojlp31.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=primenico@gmail.com \
/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.