public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Seth David Schoen <schoen@loyalty.org>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: Alejandro Colomar <alx.manpages@gmail.com>,
	mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Dear linux man-pages maintainer,
Date: Sat, 11 Mar 2023 21:47:10 -0800	[thread overview]
Message-ID: <20230312054710.GB441010@demorgan> (raw)
In-Reply-To: <20230312052006.GF7927@Debian-50-lenny-64-minimal>

Helge Kreutzmann writes:

> Sigh, learning more and more the finer details of English.
> 
> I just wonder, since these are technical documents, if this is
> supporting understanding or reducing it? Personllay I prefer one word
> for one concept.

There's a commonly-suggested rule in style guides that "open" compound
nouns (those still written as multiple distinct words) should be
hyphenated when used to modify another noun, but not when an open
compound noun occurs as a noun by itself.

So for example, we might have "Richard Stallman wrote several
free-software licenses", but "Richard Stallman originated the modern
concept of free software".

This is described, for example, at

https://www.merriam-webster.com/words-at-play/hyphen-rules-open-closed-compound-words

although this source is less prescriptive and definitive than some
others.

That source also describes a trend where newly-coined English compounds
are usually regarded as separate words for some time, but people
increasingly see them as single words (with a multiword etymology) after
acquiring greater familiarity with them.  In this case, it seems that
the man page editors feel that "run level" is too unfamiliar or recent
as a technical term to be widely understood as a single word (so my
intuition -- that it could be a single word -- is, in a way, further
along in the process).  The Merriam-Webster article seems to imply that,
after a few more decades, more people may become comfortable with
"runlevel" as a single word, assuming we continue to use that same term
frequently for the same concept.

The hyphenation rule for an open compound (in the sense described in
the Merriam-Webster article) modifying another noun, as opposed to an
open compound standing alone as a noun, is not completely universal and
might not be understood by all English learners, but it's a rule that's
very, very commonly suggested by teachers and grammar references.  It
would not be uncommon for both native and non-native English speakers to
have been taught some version of this rule in school at some point.

We might sort of analogize it to the German rule for the case where a
proper name is used as a part of the proper name of something else
(like a street, school, or prize).  There German expects to hyphenate
the entire resulting phrase, like

Heinrich-Böll-Preis
Kaiser-Wilhelm-Universität
Karl-Marx-Allee
Käthe-Kollwitz-Preis
Max-Ernst-Stipendium
Richard-Strauss-Straße
Sankt-Johann-der-Täufer-Kirche

even though the original proper names (Heinrich Böll, Kaiser Wilhelm,
Karl Marx, etc.) aren't hyphenated when used in their original sense to
refer to _people_.  While this English rule isn't exactly the same,
it also shows a propensity for using a hyphen when a noun is used in
one context, but not when the same noun is used in a different context.

  reply	other threads:[~2023-03-12  5:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-11 17:13 Dear linux man-pages maintainer, Helge Kreutzmann
2023-03-11 18:56 ` Seth David Schoen
2023-03-11 19:51   ` Helge Kreutzmann
2023-03-11 23:29   ` Alejandro Colomar
2023-03-11 23:38     ` Alejandro Colomar
2023-03-12  5:20     ` Helge Kreutzmann
2023-03-12  5:47       ` Seth David Schoen [this message]
2023-03-12  6:02         ` Helge Kreutzmann
2023-03-12 11:05           ` Alejandro Colomar

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=20230312054710.GB441010@demorgan \
    --to=schoen@loyalty.org \
    --cc=alx.manpages@gmail.com \
    --cc=debian@helgefjell.de \
    --cc=linux-man@vger.kernel.org \
    --cc=mario.blaettermann@gmail.com \
    /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