All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: "Pali Rohár" <pali@kernel.org>
Cc: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	linux-man@vger.kernel.org
Subject: Re: [PATCH] termios.3: Use bold style for Bnn and EXTn macro constants
Date: Fri, 30 Jul 2021 09:04:22 +1000	[thread overview]
Message-ID: <20210729230421.lm65cjomqx6rezzl@localhost.localdomain> (raw)
In-Reply-To: <20210729172320.xhrbonoxisqioe3e@pali>

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

At 2021-07-29T19:23:20+0200, Pali Rohár wrote:
> How do you prefer to format this part? \fBB0\fP, ..., \fBB9600\fP

I'd use the B or BR macro to set the literals, depending on whether they
are directly followed by something that should be in the roman style,
and I would definitely set the ellipsis in roman; when used as such,
it should never be set in bold or italics.  Use of the ellipsis in *roff
input requires some care, which is unfortunately often neglected.

.BR B0 ,
\&.\|.\|.\|,
.B 9600

(I dithered over inclusion of the thin space escape sequence \| between
the ellipsis and the comma.  I can see arguments either way, and a quick
Internet search does not suggest to me a strong wind in either
direction.  Since its presence or absence makes no difference for
terminal output, I expect most writers of man pages won't care.)

Regards,
Branden

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

  reply	other threads:[~2021-07-29 23:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-25 22:54 [PATCH] termios.3: Use bold style for Bnn and EXTn macro constants Pali Rohár
2021-07-29 11:21 ` Alejandro Colomar (man-pages)
2021-07-29 17:23   ` Pali Rohár
2021-07-29 23:04     ` G. Branden Robinson [this message]
2021-07-29 23:41       ` Alejandro Colomar (man-pages)
2021-07-30  0:21         ` Pali Rohár
2021-07-30  0:53           ` G. Branden Robinson
2021-07-30 10:32 ` [PATCH v2] " Pali Rohár
2021-07-30 18:17   ` Alejandro Colomar (man-pages)

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=20210729230421.lm65cjomqx6rezzl@localhost.localdomain \
    --to=g.branden.robinson@gmail.com \
    --cc=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=pali@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.