git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Holger Hellmuth (IKS)" <hellmuth@ira.uka.de>
To: Ralf Thielow <ralf.thielow@gmail.com>
Cc: "Jens Lehmann" <Jens.Lehmann@web.de>,
	"Jan Engelhardt" <jengelh@inai.de>,
	"Thomas Rast" <trast@inf.ethz.ch>,
	"Ralph Haußmann" <ralph@scanmyfood.de>,
	"Christian Stimming" <stimming@tuhh.de>,
	"Sven Fuchs" <svenfuchs@artweb-design.de>,
	git <git@vger.kernel.org>, "Jan Krüger" <jk@jk.gs>
Subject: Re: English/German terminology, git.git's de.po, and pro-git
Date: Thu, 16 May 2013 10:48:37 +0200	[thread overview]
Message-ID: <51949D65.7050001@ira.uka.de> (raw)
In-Reply-To: <CAN0XMOJ7hRwTAR+i8_C2z2NmmcycLQkiya0ayfWS0vAw3-zqkg@mail.gmail.com>


> +    bare repository        = bloßes Repository

Since "bloßes Rep." does not convey any sensible meaning to a german 
reader (at least it doesn't to me) it might as well be "bare". Also bare 
is used as parameter to commands

> +    remote tracking branch = externer Übernahmezweig

Anyone used to the english client will switch as soon as he has to read 
this. No idea how to improve that though except to just use the english 
terms like the pro git translation does.

> +    upstream branch        = -||-

Use upstream as it is used as parameter to commands

> +    fetch = anfordern
fetch = fetch
> +    pull  = zusammenführen
pull = pull
> +    push  = versenden
push = push

established vocabulary used in stack programming as well as in vcs. 
Should not be translated.

> +    clean(verb)        =
clean(verb) = säubern/aufräumen
> +    clean(noun)        =
clean(noun) = Säuberung

"aufräumen" is the better verb but there is no noun for it.

> +    whitespace         = Leerzeichen (FIXME?) (maybe "Leerraum")
whitespace = whitespace

There is no german word for whitespace

> +Still being worked out:
> +
> +    prune              = veraltete(n) Zweig(e) entfernen
> +    checkout(verb)     = auschecken
> +
> +    git add      = hinzufügen

"mittels "git add" hinzufügen" if you want to emphasize that you add 
something with the command

> +
> +    merge conflict = Merge-Konflikt
> +    3-way merge    = 3-Wege-Merge
> +    paths          = Pfade
> +
> +    symbolic link = symbolische Verknüfung
> +    path = Pfad
> +    link = Verknüpfung
> +
> +    reflog = Referenzprotokoll
> +    partial commit = teilweise committen, partiell committen

As a noun, "Teil-Commit"

> +
> +    reset = neu setzen (maybe "umsetzen"?)

"zurücksetzen"

  reply	other threads:[~2013-05-16  8:48 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-13 12:54 English/German terminology, git.git's de.po, and pro-git Thomas Rast
2013-05-13 13:57 ` 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) [this message]
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=51949D65.7050001@ira.uka.de \
    --to=hellmuth@ira.uka.de \
    --cc=Jens.Lehmann@web.de \
    --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 \
    --cc=trast@inf.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).