From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v4 08/10] intro.3: wfix
Date: Sun, 8 Jan 2023 17:08:00 -0600 [thread overview]
Message-ID: <20230108230800.yjdtzqjmmhzvmjw6@illithid> (raw)
In-Reply-To: <742a9348-23b7-b3f1-099a-85d30e3eac61@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1947 bytes --]
Hi Alex,
At 2023-01-07T20:47:20+0100, Alejandro Colomar wrote:
> See a few comments below (as you asked in another email).
> > > +The Linux
> > > +.I man-pages
>
> The Linux man-pages is a singular noun that denominates the project.
> Using it as a plural noun that refers to the pages contained in it
> sounds weird.
In English this is a slippery area. In U.S. English nouns referring to
collections tend to be singularized, whereas in Commonwealth English
they tend to the plural, but exceptions are seen in both dialects[1] and
the meaning is usually clear.
> I find the new wording more confusing than the original.
I'll recast, then.
> > > +organize section 3 into subsections
> > > that reflect the complex structure of the standard C library
> > > -and its many implementations:
> > > +and its many implementations.
> > > +.IR libc 's
> > > +difficult history frequently makes it a poor example to follow
> > > +in design,
> > > +implementation,
> > > +and presentation.
> > > .IP \(bu 3
> > > 3const
> > > .IP \(bu
> > > @@ -87,11 +93,6 @@ and its many implementations:
> > > .IP \(bu
> > > 3type
> > > .PP
>
> The list of subsections seems more connected to "organize section 3
> into subsections", rather than with the comment about libc's
> organization being crap. I think that is fine after reading the list,
> stating that what you just read is crap, but necessary crap due to
> libc's history.
It read more poorly to me that way. My presentation was grounded on my
recollection that we agreed that these new subsections of yours would
not be necessary if the standard C library were not (1) huge and (2)
disorganized.
I'll take another crack at it, supplying a bit more motivation but
trying not to recapitulate our discussion, which doesn't demand that
degree of preservation. :P
Regards,
Branden
[1] https://languagelog.ldc.upenn.edu/nll/?p=877
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-01-08 23:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 9:55 [PATCH v4 08/10] intro.3: wfix G. Branden Robinson
2023-01-07 12:45 ` Alejandro Colomar
2023-01-07 12:57 ` Alejandro Colomar
2023-01-07 16:45 ` G. Branden Robinson
2023-01-07 16:20 ` G. Branden Robinson
2023-01-07 19:47 ` Alejandro Colomar
2023-01-08 23:08 ` G. Branden Robinson [this message]
2023-01-09 12:14 ` 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=20230108230800.yjdtzqjmmhzvmjw6@illithid \
--to=g.branden.robinson@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.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