From: Jens Lehmann <Jens.Lehmann@web.de>
To: Jan Engelhardt <jengelh@inai.de>
Cc: "Holger Hellmuth (IKS)" <hellmuth@ira.uka.de>,
"Ralf Thielow" <ralf.thielow@gmail.com>,
"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: Wed, 15 May 2013 14:27:25 +0200 [thread overview]
Message-ID: <51937F2D.90608@web.de> (raw)
In-Reply-To: <alpine.LNX.2.01.1305151351130.20281@nerf07.vanv.qr>
Am 15.05.2013 13:56, schrieb Jan Engelhardt:
> On Wednesday 2013-05-15 13:26, Jens Lehmann wrote:
>> 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
>
> While it's spoken Packdatei, the way to actually write it is
> .pack-Datei or ".pack"-Datei.
I actually had the '-' in there too until I tried to look up "Zip-Datei"
in the Duden. While I don't get the leading '.' (I cannot remember having
seen that anywhere, AFAIK the file extensions are always used without the
dot), I'm not a grammar expert and will be fine either way.
>> extension ".zip" is a "Zipdatei" (known by the Duden)
>
> If that's how Duden specifies it, it's time to call wrong upon Duden.
Go ahead: http://www.duden.de/rechtschreibung/Zipdatei ;-)
>> 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")
>
> Not so strange. We have other words with -tet.
> bitten -> erbittete -> habe erbittet.
That example was not the best, what about "wenn Du das mergest(?)" (if
you merge that), I cannot really say how to write that correctly (as in
German we would want to drop the last 'e', right?). All that goes away
when we use "Merge" as a noun: "wenn Du den Merge machst". But again,
somebody else might come up with a grammatically correct solution for
that I'm missing.
next prev parent reply other threads:[~2013-05-15 12:28 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 [this message]
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=51937F2D.90608@web.de \
--to=jens.lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=hellmuth@ira.uka.de \
--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 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.