public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: alx.manpages@gmail.com, mario.blaettermann@gmail.com,
	linux-man@vger.kernel.org
Subject: Re: Issue in man page wctype.3
Date: Sun, 22 Jan 2023 14:01:49 -0600	[thread overview]
Message-ID: <20230122200149.54quo22te2kckbee@illithid> (raw)
In-Reply-To: <20230122193133.GA29288@Debian-50-lenny-64-minimal>

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

Hi Helge,

At 2023-01-22T20:31:33+0100, Helge Kreutzmann wrote:
> Without further ado, the following was found:
> 
> Issue:    all locales. → all locales:
> 
> "The B<wctype>()  function returns a property, given by its name.  The set of "
> "valid names depends on the B<LC_CTYPE> category of the current locale, but "
> "the following names are valid in all locales."

I disagree with this.  The material that follows does not serve to end
the sentence; it is a displayed list of items with no grammatical
structure.

The colon in English must be followed by an independent clause. (A list
of comma-separated items, or a list of semicolon-separated items that
contain commas is tolerated after a colon by some style guides.)

It is distressingly common that, in particular, programmers use colons
as a hatch for escaping the rules of English grammar, but it is _not_
correct usage, and any migration should be away from this practice, not
toward it.

Regards,
Branden

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

  reply	other threads:[~2023-01-22 20:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22 19:31 Issue in man page wctype.3 Helge Kreutzmann
2023-01-22 20:01 ` G. Branden Robinson [this message]
2023-01-22 20:04   ` Helge Kreutzmann

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=20230122200149.54quo22te2kckbee@illithid \
    --to=g.branden.robinson@gmail.com \
    --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