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 v3 07/13] libc.7: ffix
Date: Thu, 5 Jan 2023 18:17:19 -0600 [thread overview]
Message-ID: <20230106001719.imokpcfcqbuuuxka@illithid> (raw)
In-Reply-To: <7aa64afd-86ea-fa04-9e97-98b60ff8b264@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1349 bytes --]
Hi Alex,
At 2023-01-06T00:53:11+0100, Alejandro Colomar wrote:
> On 1/5/23 23:53, G. Branden Robinson wrote:
> > * Set page topic in lowercase.
> > * Use typographer's quotation marks instead of '"' for quotation.
>
> Isn't it equivalent in running text? '"' is simpler to type.
No, it's not equivalent anywhere except on the "ascii", "latin1", and
"cp1047" output devices.
$ groff -man -Tpdf <<EOF > quote.pdf
.TH foo 1 2023-01-05 "groff test suite"
.SH Name
foo \- "frobnicate" a \(lqbar\(rq
EOF
$ evince quote.pdf
It _is_ simpler to type just ", and many other man page authors seem to
have found it so. That is why I have proposed a `Q` quotation macro,
because without it, man page authors seem to forego quotation entirely
in favor of italics, bold, or nothing.
https://lists.gnu.org/archive/html/groff/2022-12/msg00078.html
Historically, TeX-style quotation ``like this'' has been seen in *roff
documents, but the practice is almost nonexistent in the Linux man-pages
corpus.
``This'' is so ugly on ISO 8859 and later character set-based terminals
that I don't wonder why people avoid it.
https://www.open-std.org/JTC1/SC2/WG3/docs/n411.pdf
...is a copy of part 1 of ECMA-94, the gratis equivalent of ISO 8859,
and shows what the ' and ` glyphs are supposed to look like.
Regards,
Branden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-01-06 0:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 22:53 [PATCH v3 07/13] libc.7: ffix G. Branden Robinson
2023-01-05 23:53 ` Alejandro Colomar
2023-01-06 0:17 ` G. Branden Robinson [this message]
2023-01-06 0:39 ` Alejandro Colomar
2023-01-06 7:25 ` G. Branden Robinson
[not found] ` <20230106071642.ukwraci3kp5sa74r@illithid>
2023-01-06 12:06 ` Alejandro Colomar
2023-01-06 7:24 ` How Groupe Bull screwed French with ISO 8859-1 (was: [PATCH v3 07/13] libc.7: ffix) G. Branden Robinson
2023-01-06 23:40 ` [PATCH v3 07/13] libc.7: ffix Alejandro Colomar
2023-01-08 22:59 ` G. Branden Robinson
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=20230106001719.imokpcfcqbuuuxka@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