All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Rast <trast@inf.ethz.ch>
To: Ralf Thielow <ralf.thielow@gmail.com>,
	Christian Stimming <stimming@tuhh.de>,
	Sven Fuchs <svenfuchs@artweb-design.de>,
	Ralph Haussmann <ralph@scanmyfood.de>
Cc: git@vger.kernel.org, "Jan Engelhardt" <jengelh@inai.de>,
	"Jan Krüger" <jk@jk.gs>
Subject: English/German terminology, git.git's de.po, and pro-git
Date: Mon, 13 May 2013 14:54:51 +0200	[thread overview]
Message-ID: <87k3n36nvo.fsf@linux-k42r.v.cablecom.net> (raw)

Hi

I hope I got together a Cc list that pretty much represents everyone
involved in git core and pro-git book translation into German.

As I am sure you are all aware, there are two main religions as to how
one can translate technical material into German: leave the technical
terms mostly in English, or translate them to an appropriate
corresponding word.  I'll denote them G+E and Ger, respectively.  I
would really like to avoid rehashing that entire discussion in this
thread, if at all possible; we've flogged that horse enough.  See
e.g. [1] for previous threads on the git list about the transation.

However, an unfortunate and unsatisfactory situation has developed:
Christian Stimming's git-gui de.po uses a Ger translation, and Ralf
Thielow built core git's de.po on top of it, so it's also Ger.

Meanwhile, and independently, Sven Fuchs and Ralph Haussmann wrote a
translation of pro-git (which is also quite mature at this point, having
apparently begun in 2009), and as you probably guessed by now, it's G+E.

So that leaves us at a point where "the" libre Git book (and also the
one that happens to be hosted on git-scm.com, the official site) does
not match the terminology used by German git.

Like, at all.  They're not even remotely near each other.

Therefore, a total newbie would find at least one of those two totally
useless.  I haven't done a comprehensive survey yet, but it is my
impression that the commercial git books are also G+E, so the
hypothetical newbie would be stuck learning the English terms in one of
the two regardless.

So where to go from this mess?

Obviously -- unless the agreement is that the status quo should persist
-- we'd first have to sort out what the preferable translation should
be.  And I'm a bit scared of trying, except that a straw poll on IRC
gave me some hope that a simple majority vote could help settle it.

My vote is G+E.

After that, we should create a unified glossary.  Even in the G+E case,
a few terms would presumably be translated fully and some others might
have partial translations (checkout -> auschecken?).  The current
glossary for git's de.po is [2].  I have no idea what Sven and Ralph do.
Perhaps a github wiki page would be fine for everyone?

Finally, converting the existing translation will require some manpower.
I'll help review things, as I have previously done for translation
updates of core git de.po; perhaps with a few more volunteers it can be
done pretty quickly.

Thanks for your time.

- Thomas



[1]  http://thread.gmane.org/gmane.comp.version-control.git/58315
     http://thread.gmane.org/gmane.comp.version-control.git/156226/focus=156373
     http://thread.gmane.org/gmane.comp.version-control.git/196779/focus=196792

[2]  https://github.com/ralfth/git-po-de/wiki/Glossary

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

             reply	other threads:[~2013-05-13 12:55 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-13 12:54 Thomas Rast [this message]
2013-05-13 13:57 ` English/German terminology, git.git's de.po, and pro-git Jan Engelhardt
2013-05-13 17:19   ` Jens Lehmann
2013-05-13 18:57   ` AW: " Ralph Haußmann
2013-05-13 19:25     ` Jan Engelhardt
2013-05-14 17:51       ` Ralf Thielow
2013-05-15 10:23         ` Holger Hellmuth (IKS)
2013-05-15 11:26           ` Jens Lehmann
2013-05-15 11:56             ` Jan Engelhardt
2013-05-15 12:27               ` Jens Lehmann
2013-05-15 13:14                 ` Jan Engelhardt
2013-05-15 15:31                   ` Holger Hellmuth (IKS)
2013-05-15 17:28                     ` Jan Engelhardt
2013-05-16  5:57             ` Ralf Thielow
2013-05-16  8:48               ` Holger Hellmuth (IKS)
2013-05-19 16:06                 ` Ralf Thielow
2013-05-19 16:56                 ` Ralf Thielow
2013-05-20  4:01                   ` Holger Hellmuth
2013-05-22 14:09                     ` Ralf Thielow
2013-05-16  9:00               ` Thomas Rast
2013-05-19 16:49                 ` Ralf Thielow
2013-05-19 16:53               ` Ralf Thielow
2013-05-20 19:41                 ` Christian Stimming
2013-05-22 15:16                   ` Ralf Thielow
2013-05-22 15:52                     ` Holger Hellmuth (IKS)
2013-05-22 16:43                       ` Jan Engelhardt
2013-05-23 18:16                     ` Bernhard R. Link
2013-05-24 16:41                       ` Ralf Thielow
2013-06-16 21:22                       ` Jan Engelhardt
2013-05-24 16:51                 ` Ralf Thielow
2013-05-13 16:30 ` Ralf Thielow
2013-05-16 10:49 ` Christian Stimming

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=87k3n36nvo.fsf@linux-k42r.v.cablecom.net \
    --to=trast@inf.ethz.ch \
    --cc=git@vger.kernel.org \
    --cc=jengelh@inai.de \
    --cc=jk@jk.gs \
    --cc=ralf.thielow@gmail.com \
    --cc=ralph@scanmyfood.de \
    --cc=stimming@tuhh.de \
    --cc=svenfuchs@artweb-design.de \
    /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.