From: Junio C Hamano <gitster@pobox.com>
To: Christian Stimming <christian@cstimming.de>
Cc: Pratyush Yadav <me@yadavpratyush.com>, git@vger.kernel.org
Subject: Re: [PATCH 2/3] git-gui: update german translation
Date: Mon, 27 Jan 2020 11:02:44 -0800 [thread overview]
Message-ID: <xmqqimkwbu3v.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <1910399.tNsU6uBNYh@ckiste> (Christian Stimming's message of "Sun, 26 Jan 2020 16:52:15 +0100")
Christian Stimming <christian@cstimming.de> writes:
> Dear Pratyush,
>
> thanks for the first evaluation.
>
> Am Samstag, 25. Januar 2020, 17:56:29 CET schrieb Pratyush Yadav:
>> > Subject: Re: [PATCH 2/3] git-gui: update german translation
>>
>> Nitpick: capitalise "german". So, s/german/German/
>
> Of course I can do that... however, the capitalization of the headline is
> somewhat different every time in the repository. The first word is lower case,
> yes, but e.g. the language adjective is sometimes upper case, sometimes lower
> case.
>
>> On 24/01/20 10:33PM, Christian Stimming via GitGitGadget wrote:
>> > From: Christian Stimming <christian@cstimming.de>
>> >
>> > Switch several terms from uncommon translations back to english
>> > vocabulary, most prominently commit (noun, verb) and repository. Adapt
>> > glossary and translation accordingly.
>>
>> Can you also explain _why_ these uncommon translations are changed to
>> English vocabulary?
>
> I've written an explanation in the cover letter email. Do you want to have it
> copied into the commit message?
It is unclear to me how these translation patches were split into
three. I am sort-of guessing that 1/3 is only to cover the new
entries in .pot that have no corresponding entries in translation,
and the rest is to update/fix existing translations, but I do not
know how these changes are split between 2/3 and 3/3. In any case,
"we must update original translation that does not match accepted
computer lingo" you wrote in the cover letter sounds like a very
good justification to record in the commit that updates/fixes the
existing entries.
next prev parent reply other threads:[~2020-01-27 19:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 22:33 [PATCH 0/3] git gui: improve German translation Christian Stimming via GitGitGadget
2020-01-24 22:33 ` [PATCH 1/3] git-gui: update german translation to most recently created pot templates Christian Stimming via GitGitGadget
2020-01-24 22:33 ` [PATCH 2/3] git-gui: update german translation Christian Stimming via GitGitGadget
2020-01-25 16:56 ` Pratyush Yadav
2020-01-26 15:52 ` Christian Stimming
2020-01-27 19:02 ` Junio C Hamano [this message]
2020-01-28 18:40 ` Pratyush Yadav
2020-01-24 22:33 ` [PATCH 3/3] git-gui: completed " Christian Stimming via GitGitGadget
2020-01-25 17:01 ` Pratyush Yadav
2020-02-09 22:00 ` [PATCH v2 0/3] git gui: improve German translation Christian Stimming via GitGitGadget
2020-02-09 22:00 ` [PATCH v2 1/3] git-gui: update pot template and German translation to current source code Christian Stimming via GitGitGadget
2020-02-09 22:00 ` [PATCH v2 2/3] git-gui: extend translation glossary template with more terms Christian Stimming via GitGitGadget
2020-02-09 22:00 ` [PATCH v2 3/3] git-gui: update German translation Christian Stimming via GitGitGadget
2020-02-17 15:50 ` [PATCH v2 0/3] git gui: improve " Pratyush Yadav
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqimkwbu3v.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=christian@cstimming.de \
--cc=git@vger.kernel.org \
--cc=me@yadavpratyush.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).