All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Christian Stimming <stimming@tuhh.de>,
	Stefan Beller <sbeller@google.com>
Cc: Ralf Thielow <ralf.thielow@gmail.com>,
	"git@vger.kernel.org" <git@vger.kernel.org>,
	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: Tue, 02 Jun 2015 10:22:36 +0200	[thread overview]
Message-ID: <556D67CC.3000400@drmicha.warpmail.net> (raw)
In-Reply-To: <1749852.uCRPrjoCKZ@cs-pc>

Christian Stimming venit, vidit, dixit 01.06.2015 22:00:
> Am Montag, 1. Juni 2015, 12:34:31 schrieb Stefan Beller:
>> On Mon, Jun 1, 2015 at 12:26 PM, Christian Stimming <stimming@tuhh.de> 
> wrote:
>>> "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..."
>>
>> So the *** is cut out here, or do you literally advise to think of a
>> black magic box here?
>> I'd be interested to know your preferred translation, maybe that can
>> be used instead of Staging-Area then?
> 
> Sorry for being unclear here: I left out the concrete word I use because you 
> might need to come up with your own choice in the command-line git 
> translation. The point of this remark is rather that almost any other term is 
> better than leaving "index" as a term as-is. The term that I use is only one 
> among probably many possibilities.
> 
> In case you still want to know my preferred German word, I stick to the 
> translations that are used in git-gui, mostly still proposed by myself in 
> (huh) 2008. http://repo.or.cz/w/git-gui.git/blob/HEAD:/po/glossary/de.po  
> There, "index" isn't used in the user interface anymore but rather "staging 
> area", and that's translated into German as "Bereitstellung". In my experience 
> this term works quite well for a German-speaking developer audience, even 
> though the term with its military background is only seldomly used or known. 
> But the word triggers some well-suited associations: partly "bereit" for the 
> next step, partly "Stellung" as some extra third place in addition to working 
> copy and repository. But that might very well be a different discussion than 
> what you need to discuss for command line git.
> 
> Regards,
> 
> Christian
> 

git-gui in German is unusable for any user who knows German and knows
the technical terms used in git but not the specific choices the git-gui
translator has made. It's a great example of how not to do a translation.

Also, a translation is really the wrong place to "correct" choices made
upstream in the main project. There it is index, not staging area (for a
good reason).

The purpose of a translation is to make it easier for non-native users
to use a tool by translating (parts of) the interface into their
language - not to make it more difficult for them to use the other parts.

Michael

  reply	other threads:[~2015-06-02  8:22 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
2015-06-01 19:34     ` Stefan Beller
2015-06-01 20:00       ` Christian Stimming
2015-06-02  8:22         ` Michael J Gruber [this message]
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=556D67CC.3000400@drmicha.warpmail.net \
    --to=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=stimming@tuhh.de \
    --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 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.