git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Stimming <stimming@tuhh.de>
To: git@drmicha.warpmail.net
Cc: Ralf Thielow <ralf.thielow@gmail.com>,
	git@vger.kernel.org, sbeller@google.com, tr@thomasrast.ch,
	jk@jk.gs, phillip.szelat@gmail.com, matthias.ruester@gmail.com,
	magnus.goerlitz@googlemail.com
Subject: Re: [PATCH] l10n: de.po: translate "index" as "Index"
Date: Mon, 01 Jun 2015 21:26:48 +0200	[thread overview]
Message-ID: <3813728.oJDPxEPYet@cs-pc> (raw)
In-Reply-To: <556C0BFD.3060806@drmicha.warpmail.net>

Am Montag, 1. Juni 2015, 09:38:37 schrieb git@drmicha.warpmail.net:
> Ralf Thielow venit, vidit, dixit 29.05.2015 20:54:
> > The term "index" is translated as "Staging-Area" to
> > not confuse beginners who don't know about Git's index.
> > 
> > Since the term "staging area" doesn't appear in original
> > Git messages (not even in the glossary) and "index" is a
> > well known term for experienced users, we should treat
> > "index" as a Git term and therefore don't translate it.
> 
> Super! :)

Sorry to contradict, but: No, not super.

Again I question the whole point of such a denglish translation. Do you want 
to present the git wording to those experienced users who know git anyway? 
Then you are probably better off suggesting those guys to stick to the 
original English messages. Or do you want to describe what's going on in a 
language that somewhat resembles understandable German? In that case, "Index" 
is a particularly bad choice to keep as an unchanged word. 

To make things even worse, "index" is a particularly bad wording choice in 
English in the first place. Why? Because the e.g. git book of course has an 
"index": That's the page where you can look up certain keywords that will then 
reference you to the place where those words are being used. It never occurred 
to me why anyone on earth ever thought this word might give a good metaphor 
for what it should mean in the git context. Well, maybe some internal code 
gurus will now immediately argue how this is exactly how git's index works 
internally. Guess what? As a git user, this is not a single bit of how the 
index concept is visible to the user. As a git user, the index has something 
to do with "already but not yet", or with "not only in the working copy but 
also already somewhere else", or with "not yet in a commit but somewhat half-
way there". All those points could maybe be captured in some other wording, 
but for sure neither in the English "index" nor (and even less) in a German 
"Index". 

Hence, if the word isn't part of a command name, the translators are free to 
decide which word to use, and you could probably choose some word that is 
actually helpful in the target language. "Index" is not. In case you belong to 
the 0.5% of version control users who are experienced enough with git to know 
and understand the English term "index", feel free to stick with that word. 
But in case you target this translation to the somewhat majority of version 
control users, I suggest you better think again.  Thanks for reading.

Best Regards,

Christian


PS: Just for the record: If I explain git to new users and we reach the 
"index" concept, my explanation routinely says "This concept is called 'index' 
but it has nothing to do with any associations you make with that word. Better 
remember this thingy as *** and replace the termin 'index' with *** every time 
you read about it." where "***" is my preferred translation. The facial 
expressions of the audience regarding "index" regularly confirm this approach 
as the better one. I never encountered anyone who says "Oh, but isn't 'index' 
a much better term for this than what you said..."

  parent reply	other threads:[~2015-06-01 19:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29 18:54 [PATCH] l10n: de.po: translate "index" as "Index" Ralf Thielow
2015-06-01  7:38 ` git
2015-06-01 15:10   ` phillip
2015-06-02  8:34     ` Michael J Gruber
2015-06-01 19:26   ` Christian Stimming [this message]
2015-06-01 19:34     ` Stefan Beller
2015-06-01 20:00       ` Christian Stimming
2015-06-02  8:22         ` Michael J Gruber
2015-06-05 19:20     ` Ralf Thielow
2015-06-02 16:07   ` Ralf Thielow
2015-06-05 17:41 ` [PATCH v2] " Ralf Thielow
2015-06-12 18:15   ` [PATCH v3] " Ralf Thielow

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=3813728.oJDPxEPYet@cs-pc \
    --to=stimming@tuhh.de \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=jk@jk.gs \
    --cc=magnus.goerlitz@googlemail.com \
    --cc=matthias.ruester@gmail.com \
    --cc=phillip.szelat@gmail.com \
    --cc=ralf.thielow@gmail.com \
    --cc=sbeller@google.com \
    --cc=tr@thomasrast.ch \
    /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).