From: "Holger Hellmuth (IKS)" <hellmuth@ira.uka.de>
To: Ralf Thielow <ralf.thielow@gmail.com>
Cc: "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>,
jens.lehmann@web.de
Subject: Re: English/German terminology, git.git's de.po, and pro-git
Date: Wed, 15 May 2013 12:23:20 +0200 [thread overview]
Message-ID: <51936218.9020306@ira.uka.de> (raw)
In-Reply-To: <CAN0XMOL3rkYDinSCN2GLaRj7dOvbF=SdMRxM4PHCZ5h7g5Nkkw@mail.gmail.com>
Am 14.05.2013 19:51, schrieb Ralf Thielow:
> - repository = Projektarchiv
> - bare repository = bloßes Projektarchiv
> + repository = Projektarchiv, (or just Repository?)
> + bare repository = bloßes Projektarchiv (-||-), (reines, pures Repository)
I would vote for Repository or if it needs to be translated, simply
Archiv. Neither Projektarchiv nor Archiv is commonly used by me but
Archiv is shorter and not everything in a repository is a project.
> I'm not sure about using "Repository". I think "Projektarchiv" is
> actually good enough.
>
> - committer = Eintragender
> - tagger = Markierer
> + committer = Eintragender (or Committer, Commit-Ersteller)
> + tagger = Markierer (or Tagger, Tag-Ersteller)
> ...[each usage of commit and tag]...
Both "commit" and "tag" are used in commands so with the exception of
the place where they are defined the english words should be used. I
think Commit-/Tag-Ersteller actually sounds fine and german enough so no
one notices there is an english word in there ;-)
> + branch = Zweig (or Branch)
>
> I think "Zweig" is already fine.
Same reason, branch is used as a command and should not be translated.
But "Zweig" is a really natural and together with "Baum" fitting
translation, so I'm conflicted here.
next prev parent reply other threads:[~2013-05-15 10:45 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) [this message]
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=51936218.9020306@ira.uka.de \
--to=hellmuth@ira.uka.de \
--cc=git@vger.kernel.org \
--cc=jengelh@inai.de \
--cc=jens.lehmann@web.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).