git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Engelhardt <jengelh@inai.de>
To: "Holger Hellmuth (IKS)" <hellmuth@ira.uka.de>
Cc: "Jens Lehmann" <Jens.Lehmann@web.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 19:28:12 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.01.1305151924240.8332@nerf07.vanv.qr> (raw)
In-Reply-To: <5193AA61.2040205@ira.uka.de>


On Wednesday 2013-05-15 17:31, Holger Hellmuth (IKS) wrote:
>>>
>>> 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.
>>
>> In UNIX-land, extension seemed to always include the dot.
>> In DOS-land, it's without (inherited from VMS too, perhaps?)
>> As such, either way to write it is acceptable.
>
> Even in unix-land no one adds a dot because usually the extension is named
> after the data format, only that the file extension is used as the common
> abbreviation (at least that is my interpretation). Compare with jpeg. You often
> write jpeg-Datei instead of jpg-Datei because the data format is called jpeg.

That too is correct, and actually a third way of describing files.
For example, .doc/.xls-Datei in speech is very seldom, if at all; MS
Office output has had generally been called Word-Datei,
Excel-Tabelle/-Datei and so on.

What I meant however is that the extension is ".jpg" (or .jpeg) from
a programming aspect (like, when naïvely trying to figure out the
filetype) as in
  ($name, $ext) = (/^[^\.]+(\..+)?/)

  reply	other threads:[~2013-05-15 17: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
2013-05-15 13:14                 ` Jan Engelhardt
2013-05-15 15:31                   ` Holger Hellmuth (IKS)
2013-05-15 17:28                     ` Jan Engelhardt [this message]
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=alpine.LNX.2.01.1305151924240.8332@nerf07.vanv.qr \
    --to=jengelh@inai.de \
    --cc=Jens.Lehmann@web.de \
    --cc=git@vger.kernel.org \
    --cc=hellmuth@ira.uka.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).