netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Alejandro Colomar <alx@kernel.org>,
	Kuniyuki Iwashima <kuniyu@amazon.com>,
	alexhenrie24@gmail.com, branden@debian.org,
	linux-man@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] rtnetlink.7: Document struct ifa_cacheinfo
Date: Wed, 6 Nov 2024 11:45:31 -0600	[thread overview]
Message-ID: <20241106174531.crictruy4scop5q2@illithid> (raw)
In-Reply-To: <20241106091801.3e021842@hermes.local>

[-- Attachment #1: Type: text/plain, Size: 2234 bytes --]

Hi Stephen,

At 2024-11-06T09:18:01-0800, Stephen Hemminger wrote:
> Alejandro Colomar <alx@kernel.org> wrote:
> > We use two spaces after period (the correct amount).  :)
> 
> Double spacing after period is a leftover from using typewriters.

No, it isn't.  See URL below.

> Modern usage is single space after period.
[...]
> 	These days most contemporary style guides also recommend using a
> 	single space between sentences, including:
> 
> 	The Chicago Manual of Style
> 	The American Psychological Association (often referred to as “APA”)
> 	Microsoft Manual of Style
> 	The Gregg Reference Manual
> 	The Associated Press Stylebook

You're not bringing any new information to the table, and you don't
appear to understand why the two-space rule is in place for _typesetting
software_.  I don't just mean *roff, but TeX as well.

Neither of these is a WYSIWYG system.  Neither of them is Markdown.

The rule is not there so that people can argue over how many space
widths should separate sentences.  The rule is there so that the
formatter knows where the boundaries between sentences _are_.

If you despise the use of two spaces between sentences in a *roff source
document, there's an easy solution: use what Alex calls "semantic
newlines".

https://www.gnu.org/software/groff/manual/groff.html.node/Sentences.html#Sentences

I furthermore remind the reader that, in GNU troff/man(7), the
intersentence space width is configurable at _rendering_ time--if the
author of the man(7) document honors one of the conventions that permits
the formatter to detect sentence boundaries.

For example...

groff_man_style(7):

Files

...

     /usr/groff/site-tmac/man.local
            Put site‐local changes and customizations into this file.

                   .\" Put only one space after the end of a sentence.
                   .ss 12 0 \" See groff(7).
                   .\" Keep pages narrow even on wide terminals.
                   .if n .if \n[LL]>80n .nr LL 80n

Arguing about the number of spaces between sentences in a discussion of
"semantic newlines" (or whatever you want to call them) is
counterproductive and wasteful of time.

Regards,
Branden

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2024-11-06 17:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05  4:14 [PATCH] rtnetlink.7: Document struct ifa_cacheinfo Alex Henrie
2024-11-05  5:53 ` Kuniyuki Iwashima
2024-11-05 11:33   ` Alejandro Colomar
2024-11-06 17:18     ` Stephen Hemminger
2024-11-06 17:44       ` Alejandro Colomar
2024-11-06 17:48         ` G. Branden Robinson
2024-11-06 17:45       ` G. Branden Robinson [this message]
2024-11-06 18:02         ` Alejandro Colomar
2024-11-11  6:17     ` Alex Henrie
2024-11-11  9:34       ` Alejandro Colomar
2024-11-09 16:27 ` Stephen Hemminger
2024-11-11  6:20 ` [PATCH man-pages v2] " Alex Henrie
2024-11-12  1:11   ` Kuniyuki Iwashima
2024-11-12  7:58     ` Alejandro Colomar
2024-11-12 23:26   ` Alejandro Colomar
2024-11-12 23:33     ` Kuniyuki Iwashima
2024-11-12 23:38       ` Alejandro Colomar
2024-11-12 23:46   ` 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=20241106174531.crictruy4scop5q2@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=alexhenrie24@gmail.com \
    --cc=alx@kernel.org \
    --cc=branden@debian.org \
    --cc=kuniyu@amazon.com \
    --cc=linux-man@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    /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).