git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Thomas Rast <trast@student.ethz.ch>
Cc: Christian Stimming <stimming@tuhh.de>,
	jk@jk.gs, avarab@gmail.com, git <git@vger.kernel.org>
Subject: Re: [PATCH 1/2] po/de.po: add German translation
Date: Wed, 15 Sep 2010 13:51:32 +0200	[thread overview]
Message-ID: <4C90B344.6060002@drmicha.warpmail.net> (raw)
In-Reply-To: <201009151147.45314.trast@student.ethz.ch>

Thomas Rast venit, vidit, dixit 15.09.2010 11:47:
> Hi Christian
> 
> Christian Stimming wrote:
>>
>> As you might guess, as the (initial) translator of git-gui I've been  
>> through this discussion before [1] and as you have noticed, I have  
>> decided to take a translation approach different from what you have  
>> recently discussed here. I deliberately tried to translate as much of  
>> the terms into German as possible. I do not agree about the importance  
>> of statements on this mailing list like "This translation translates  
>> too much terms - I cannot find the commands I'm used to". 
> [...]
>> Instead, a translation is for people who do neither know nor  
>> understand the English wording for the git concepts. For this target  
>> audience, the goal is to find a set of terms for the different git  
>> concepts which makes the concepts most easily accessible for their  
>> language. This may or may not include terms which are left at English  
>> words.
> 
> Maybe there should be two sets of translations then.
> 
> I'm only half serious, but the problem here is what I said earlier in
> the thread (referring to Jan's draft):
> 
> } In any case it roughly matches (or still stays slightly on the
> } more-German side of) the colloquial usage in my group, if that is
> } any indication.
> 
> "My group" is a bunch of CS researchers, so I can't say they fall
> outside the description above.  However, in our work we observe a very
> funny split between translating and keeping the terms in English:
> 
>   graph                               Graph
>   vertex                              Knoten
>   edge                                Kante
>   directed                            gerichtet
>   DAG (directed acyclic graph)        DAG
>   independent set                     independent set
>   cut (vertex, edge)                  cut (vertex, edge)
>   degree                              Grad
>   matching                            Matching
>   tree                                Baum
>   MST (minimum spanning tree)         MST (minimaler Spannbaum)
> 
> There are German terms for all the untranslated ones, but I rarely
> hear them in practical usage.  Books probably go for a full
> translation since they want to be normative (how should I know, it's
> been a while since I used a German book), but lectures stick to the
> half-translated version.

Any active graduate student or researcher is used to English articles
and books and doesn't need a translation at all, or could do completely
with a translated glossary.

I assume we do the (extensive!) translation work for people who could
not use Git without a translation. And that mandates translating as much
as possible (including man pages...).

As far as the various disciplines go, CS is always on the side of
importing more terms from English rather than translating. If we agree
that a group of CS researchers is the target I'm fine with it - but it
would imply backing out l10n ;)

Note that I don't want to create any bad feelings against the l10n
efforts. If it is done then I want it to be done right and not rushed, a
bad one does more harm than anything. I probably won't be contributing
to translations of commands, but I'm in for the glossary to help it have
a sound start.

Michael

  reply	other threads:[~2010-09-15 11:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-15  7:33 [PATCH 1/2] po/de.po: add German translation Christian Stimming
2010-09-15  9:47 ` Thomas Rast
2010-09-15 11:51   ` Michael J Gruber [this message]
2010-09-15 11:10 ` Michael J Gruber
2010-09-15 16:54   ` Andreas Schwab
2010-09-15 11:44 ` Thomas Hochstein
2010-09-16 10:57 ` Jan Krüger
2010-09-16 11:09   ` Ævar Arnfjörð Bjarmason
2010-09-16 11:29     ` Jens Lehmann
2010-09-16 11:51       ` Ævar Arnfjörð Bjarmason
2010-09-16 14:52       ` Junio C Hamano
2010-09-16 15:05         ` Jens Lehmann
2010-09-16 11:51   ` Michael J Gruber
2010-09-16 16:48     ` Jan Krüger
2010-09-17  7:23       ` Michael J Gruber
  -- strict thread matches above, loose matches on Subject: below --
2010-09-03 18:22 [GIT PULL] New ab/i18n series and builtin fixes Ævar Arnfjörð Bjarmason
2010-09-04  0:49 ` [PATCH 1/2] po/de.po: add German translation avarab
2010-09-06 15:41   ` Thomas Rast
2010-09-06 16:09     ` Jan Krüger
2010-09-06 17:06       ` Ævar Arnfjörð Bjarmason
2010-09-06 16:24     ` Jens Lehmann
2010-09-06 19:58       ` Tilo Schwarz
2010-09-06 17:15     ` Ævar Arnfjörð Bjarmason

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=4C90B344.6060002@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jk@jk.gs \
    --cc=stimming@tuhh.de \
    --cc=trast@student.ethz.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).