Re: English/German terminology, git.git's de.po, and pro-git
- From
Jens Lehmann <jens.lehmann@web.de>
- Date
- May 15, 2013, 11:26 UTC
- Message-ID
- <519370D3.3000306@web.de>
- In-Reply-To
- <51936218.9020306@ira.uka.de>
Am 15.05.2013 12:23, schrieb Holger Hellmuth (IKS):
Show 7 quoted lines
> 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.
Hmm, I rather tend towards using "Repository" instead of "Archiv" too, as "Archiv" can mean anything from a tar-file to a git repository, while we are talking about something very specific here (and a German might be surprised what the command "git archive" is about if we use "Archiv" here ;-). So if it has to be translated, I like "Projektarchiv" better than "Archiv" for those reasons. We can also think about using "Repo" as an abbreviated form, we often use that when talking about repositories in German. That would be a new term without ambiguity and will be pronounced pretty much correctly by all Germans too. But this remains one of the tougher questions.
And then "pack" is currently translated as "Archiv":
pack(noun) = Archiv
but I believe "Packdatei" would be a much better translation (especially as the translation of "pack(verb)" is "packen"). I find it natural that a file with the extension ".pack" is named Packdatei, just like a file with the extension ".zip" is a "Zipdatei" (known by the Duden) in German. And the Duden already knows "Pack" as an assembly of smaller parts, so we should be safe here.
Show 10 quoted lines
>> 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 ;-)
Yup, im my experience "committen" (to commit), "einchecken" (to check in), "auschecken" (to check out) und "taggen" (to tag) made it into our daily German language use. To avoid e.g. having past tenses look strange (like "committet") the combined Form ("Commit erstellt") could solve that problem.
Show 5 quoted lines
>> + 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.
Yes, Baum, Wurzel and Zweig are obviously equivalent to tree, root and branch, so I don't care much if we translate that or not.