public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: John Garry <john.g.garry@oracle.com>,
	linux-man@vger.kernel.org, djwong@kernel.org,
	ritesh.list@gmail.com
Subject: Re: [PATCH] statx.2: Update STATX_WRITE_ATOMIC filesystem support
Date: Thu, 5 Dec 2024 13:02:20 +0100	[thread overview]
Message-ID: <20241205120220.ep5llyzobecmtnfm@devuan> (raw)
In-Reply-To: <20241205103454.ihxar6bhxjcv2gzj@illithid>

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

Hi Branden,

On Thu, Dec 05, 2024 at 04:34:54AM -0600, G. Branden Robinson wrote:
> [trimming the linux-fsdevel list from CC, reasoning that it cares little
> about typography]
> 
> Hi Alex,
> 
> At 2024-12-05T11:02:10+0100, Alejandro Colomar wrote:
> > No; the comma shouldn't be in italics.
> > 
> > .B STATX_WRITE_ATOMIC
> > .RI ( stx_atomic_write_unit_min ,
> > .IR stx_atomic_write_unit_max ,
> > and
> > .IR stx_atomic_write_segments_max )
> 
> Style authorities differ on this point.[1]  At least three factors are
> in tension:
> 
> 1.  In traditional typography, one does in fact set the comma in italics
>     like the preceding word.  To some eyes, including mine, that looks
>     better.

I think this is in concordance with the other meh thing US typographers
do: put punctuation within quotes, misattributing them to the quotee.
I don't like that.

> 
> 2.  It is true that the comma is not part of the named parameter, so
>     under rules analogous to those that govern quotation marks in the
>     U.K., for instance, one would _not_ put the comma in italics.

Indeed.  Similar rules apply in Spain, AFAIR.

And this isn't documented in man-pages(7) either.  We probaby should.

> 3.  It doesn't matter all that much because unlike with literals, like
>     STATX_WRITE_ATOMIC, precise copy-and-pasting doesn't buy you much.
>     A formal argument name frequently _lacks_ a corresponding symbol of
>     the same name in source code.  Users of memmem(3) need not name
>     their parameters "needle" or "haystack".  So almost no one needs to
>     precisely aim their pointer between the final letter of the
>     parameter name and the trailing punctuation.

In PDF output it doesn't matter much, but underscoring a comma (which
will happen in terminals) is quite more egregious than just a minor
oddity when the last letter overlaps the punctuation slightly in the
PDF.  So, I'd say it matters in our case.

> 
> Given these factors, if you have a strong preference here, I think you
> should document it in man-pages(7).

I do.

> 
> Regards,
> Branden
> 
> [1] https://iconlogic.blogs.com/weblog/2011/04/writing-grammar-do-i-italicize-the-comma-after-an-italic-word.html
> 
>     https://english.stackexchange.com/questions/9878/should-punctuation-surrounding-italicised-words-be-italicised
> 
>     (The foregoing quotes the [in]famous Chicago Manual of Style, which
>     I generally like except for the malicious lies about historical
>     inter-sentence spacing practices promulgated by its editor, the
>     dreadful Russell Harper.[2])
> 
>     https://style.mla.org/comma-after-italicized-element/

I like the advice in that link.  :)

> 
> [2] https://web.archive.org/web/20171217060354/http://www.heracliteanriver.com/?p=324

Thanks for the link!  I applied this commit now:
<https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=bcf7d00fa4c7ce270f07d6e347c01b1f1e37580f>


Have a lovely day!
Alex

-- 
<https://www.alejandro-colomar.es/>

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

  reply	other threads:[~2024-12-05 12:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03 14:53 [PATCH] statx.2: Update STATX_WRITE_ATOMIC filesystem support John Garry
2024-12-04  4:55 ` Darrick J. Wong
2024-12-04 20:45 ` Alejandro Colomar
2024-12-05  9:33   ` John Garry
2024-12-05 10:02     ` Alejandro Colomar
2024-12-05 10:34       ` G. Branden Robinson
2024-12-05 12:02         ` Alejandro Colomar [this message]
2024-12-16 10:35       ` John Garry
2024-12-16 12:38         ` G. Branden Robinson
2024-12-16 12:47           ` Alejandro Colomar
2025-01-04 20:23             ` 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=20241205120220.ep5llyzobecmtnfm@devuan \
    --to=alx@kernel.org \
    --cc=djwong@kernel.org \
    --cc=g.branden.robinson@gmail.com \
    --cc=john.g.garry@oracle.com \
    --cc=linux-man@vger.kernel.org \
    --cc=ritesh.list@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