From: Alejandro Colomar <alx.manpages@gmail.com>
To: tz@iana.org, Paul Eggert <eggert@cs.ucla.edu>
Cc: linux-man@vger.kernel.org, Alejandro Colomar <alx@kernel.org>,
"G. Branden Robinson" <g.branden.robinson@gmail.com>,
Ingo Schwarze <schwarze@openbsd.org>
Subject: [PATCH v2 4/4] zic.8: Use correct letter case in page title (TH)
Date: Wed, 23 Nov 2022 14:48:31 +0100 [thread overview]
Message-ID: <20221123134827.10420-4-alx@kernel.org> (raw)
In-Reply-To: <20221123134827.10420-1-alx@kernel.org>
The Linux man-pages started using for the page title (TH) the correct
letter case that programs and identifiers have. This change was agreed
with groff(1) and mandoc(1) maintainers as an improvement, since it
provides more information to the reader of a manual page.
On 11/22/22 23:45, G. Branden Robinson wrote:
> I add that anyone who wants their man page headers to shout at them
> again can get that with (the forthcoming) groff 1.23.
>
> o The an (man) and doc (mdoc) macro packages support new `CS` and `CT`
> registers to control rendering of man page section headings and topics
> (seen in the page header), respectively, in full capitals. These
> default off (with no visible effect on pages that already fully
> capitalize such text in man page sources). The rationale is to
> encourage man page authors to preserve case distinction information in
> (or restore it to) their topics and section headings, while giving
> users (including system administrators, distributors, integrators, and
> maintainers of man(1) implementations) a way to view the rendered page
> elements in full capitals if desired.
>
>
Link: <https://git.savannah.gnu.org/cgit/groff.git/tree/NEWS?id=eac39afe3e7a86f3adbfb02ff5e33bfd69d4c224#n271>
Acked-by: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Ingo Schwarze <schwarze@openbsd.org>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
---
zic.8 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/zic.8 b/zic.8
index 4ef2482c..fd5dd315 100644
--- a/zic.8
+++ b/zic.8
@@ -2,7 +2,7 @@
.\" This page is in the public domain
.\" %%%LICENSE_END
.\"
-.TH ZIC 8
+.TH zic 8
.SH NAME
zic \- timezone compiler
.SH SYNOPSIS
--
2.38.1
next prev parent reply other threads:[~2022-11-23 13:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 13:48 [PATCH v2 1/4] zic.8: Add public domain notice Alejandro Colomar
2022-11-23 13:48 ` [PATCH v2 2/4] zic.8: s/time zone/timezone/ for consistency Alejandro Colomar
2022-11-23 18:42 ` Paul Eggert
2022-11-23 19:02 ` Alejandro Colomar
2022-11-23 19:14 ` G. Branden Robinson
2022-11-23 13:48 ` [PATCH v2 3/4] zic.8: Use correct escape sequences instead of special characters Alejandro Colomar
2022-11-23 18:18 ` G. Branden Robinson
2022-11-23 18:43 ` Paul Eggert
2022-11-26 2:31 ` Paul Eggert
2022-11-26 3:07 ` G. Branden Robinson
2022-11-26 21:19 ` G. Branden Robinson
2022-11-27 0:12 ` Paul Eggert
2022-12-13 23:24 ` G. Branden Robinson
2022-11-23 13:48 ` Alejandro Colomar [this message]
2022-11-23 18:45 ` [PATCH v2 4/4] zic.8: Use correct letter case in page title (TH) Paul Eggert
2022-11-23 18:32 ` [PATCH v2 1/4] zic.8: Add public domain notice Paul Eggert
2022-11-23 19:01 ` Alejandro Colomar
2022-11-23 19:19 ` Paul Eggert
2022-11-23 19:32 ` 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=20221123134827.10420-4-alx@kernel.org \
--to=alx.manpages@gmail.com \
--cc=alx@kernel.org \
--cc=eggert@cs.ucla.edu \
--cc=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=schwarze@openbsd.org \
--cc=tz@iana.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