From: Pratyush Yadav <me@yadavpratyush.com>
To: Christian Stimming via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Christian Stimming <christian@cstimming.de>
Subject: Re: [PATCH v2 0/3] git gui: improve German translation
Date: Mon, 17 Feb 2020 21:20:14 +0530 [thread overview]
Message-ID: <20200217155014.kytkqym7xpfdzatd@yadavpratyush.com> (raw)
In-Reply-To: <pull.525.v2.git.1581285658.gitgitgadget@gmail.com>
Hi Christian,
On 09/02/20 10:00PM, Christian Stimming via GitGitGadget wrote:
> git-gui: update/improve German translation
>
> Update translation template and translation glossary as prerequisite. Then,
> update German translation (glossary and final translation) to recent source
> code changes, but also switch several terms from uncommon translations back
> to English vocabulary, similar to the rest of git-core.
>
> This most prominently concerns "commit" (noun, verb), "repository",
> "branch", and some more. These uncommon translations have been introduced
> long ago and never been changed since. In fact, the whole German translation
> here hasn't been touched for a long time. However, in German literature and
> magazines, git-gui is regularly noted for its uncommon choice of translated
> vocabulary. This somewhat distracts from the actual benefits of this tool.
> So it is probably better to abandon the uncommon translations and rather
> stick to the common English vocabulary in git version control.
>
> The glossary is adapted to the git-core glossary at
> https://github.com/ruester/git-po-de/wiki/Translation-Guidelinesand the
> changed and updated terms are used in the actual translation accordingly.
Sorry for the late reply. Merged. Thanks.
--
Regards,
Pratyush Yadav
prev parent reply other threads:[~2020-02-17 15:50 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
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 ` Pratyush Yadav [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
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=20200217155014.kytkqym7xpfdzatd@yadavpratyush.com \
--to=me@yadavpratyush.com \
--cc=christian@cstimming.de \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@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.
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).