git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Rast <trast@student.ethz.ch>
To: Ralf Thielow <ralf.thielow@googlemail.com>
Cc: "Thomas Rast" <trast@student.ethz.ch>,
	"Jiang Xin" <worldhello.net@gmail.com>,
	"Junio C Hamano" <gitster@pobox.com>,
	"Git List" <git@vger.kernel.org>, "Jan Krüger" <jk@jk.gs>,
	"Christian Stimming" <stimming@tuhh.de>
Subject: Re: Please pull git-po master branch
Date: Wed, 2 May 2012 15:58:17 +0200	[thread overview]
Message-ID: <87ehr2znuu.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <CAN0XMOJ0PBA2qptw2Lm9HOq4SAkeZNAyOwPdvcb-uAcsxKnzwg@mail.gmail.com> (Ralf Thielow's message of "Wed, 2 May 2012 11:13:04 +0200")

Ralf Thielow <ralf.thielow@googlemail.com> writes:

> As I said I've tried to unify with the git-gui translation. Actually, I was
> wondered why they translate terms like "Tag" or "Commit" because
> I think they should be known by a Git user.
> 
> I know German books about Git using many other terms like
> "Staging" or "Index" as it is.

Well, this is getting into the eternal "German vs. Denglish"
bikeshedding war.  If you can actually cite books, that would probably
constitute a good argument in favour of changing it to the English terms
for these.  (I'd be all for it, and AFAIK so would Jan, but as I said
this has been going on for a while.)

>> * Make a glossary of the relevant terminology first.  Sadly
>>  gitglossary(7) has gotten somewhat stale, and perhaps can also benefit
>>  from an overhaul.  Ævar Arnfjörð Bjarmason recently made a list[4] of
>>  the most important terms, which is a good start.
>
> I would be happy to work together with you on these things.
> Tiny changes in the translation of basic terms can make
> a big difference.

Perhaps you could use the Github wiki feature to import Ævar's list into
a wiki in your git-de-po repository, which we could then edit?

> I don't think that it's sooo bad that it needs to get reverted.

Probably not, since that would be pointless without another minor
release.  But I am saying it should not have been fast-tracked to maint
in the first place.

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

  reply	other threads:[~2012-05-02 13:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02  2:45 Please pull git-po master branch Jiang Xin
2012-05-02  5:17 ` Junio C Hamano
2012-05-02  7:54 ` Thomas Rast
2012-05-02  9:13   ` Ralf Thielow
2012-05-02 13:58     ` Thomas Rast [this message]
2012-05-02 19:14       ` Ralf Thielow
2012-05-02 19:44         ` Christian Stimming
2012-05-02 13:49   ` [PATCH 0/5] de.po suggested updates Thomas Rast
2012-05-02 13:49     ` [PATCH 1/5] stash: make "saved" message translatable Thomas Rast
2012-05-02 16:42       ` Junio C Hamano
2012-05-02 13:49     ` [PATCH de.po 2/5] de.po: translate "bare" as "bloß" Thomas Rast
2012-05-02 13:49     ` [PATCH de.po 3/5] de.po: hopefully uncontroversial fixes Thomas Rast
2012-05-02 13:49     ` [PATCH de.po 4/5] de.po: translate "bad" as "ungültig" ("invalid") Thomas Rast
2012-05-02 13:49     ` [PATCH de.po 5/5] de.po: collection of suggestions Thomas Rast
2012-05-02 18:36       ` Ralf Thielow
2012-05-02 19:43         ` Thomas Rast
2012-05-02 19:42       ` Christian Stimming
2012-05-03  7:42         ` Thomas Rast
2012-05-03 13:12           ` [PATCH on ab/i18n] branch: remove lego in i18n tracking info strings Nguyễn Thái Ngọc Duy
2012-05-04 16:10             ` Junio C Hamano
2012-05-06 13:06               ` Nguyen Thai Ngoc Duy
2012-05-02 17:52     ` [PATCH 0/5] de.po suggested updates Ralf Thielow
2012-05-02 19:13     ` Christian Stimming
2012-05-02 16:40   ` Please pull git-po master branch Junio C Hamano
2012-05-03  4:31     ` Jiang Xin
2012-05-03  6:47       ` Junio C Hamano
2012-05-03 10:19         ` Jiang Xin
2012-05-03  7:49       ` Thomas Rast

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=87ehr2znuu.fsf@thomas.inf.ethz.ch \
    --to=trast@student.ethz.ch \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jk@jk.gs \
    --cc=ralf.thielow@googlemail.com \
    --cc=stimming@tuhh.de \
    --cc=worldhello.net@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 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).