From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: info-gnu@gnu.org, info-groff@gnu.org
Cc: groff@gnu.org, linux-man@vger.kernel.org
Subject: groff 1.24.1 released
Date: Sat, 14 Mar 2026 14:30:05 -0500 [thread overview]
Message-ID: <20260314193005.v3rbph3hcks2oltm@illithid> (raw)
[-- Attachment #1: Type: text/plain, Size: 4276 bytes --]
We are pleased to announce the availability of groff 1.24.1. Obtain
it from the GNU mirror network,
https://ftpmirror.gnu.org/groff/groff-1.24.1.tar.gz
or, if the network is for some reason inoperative, directly from GNU.
https://ftp.gnu.org/gnu/groff/groff-1.24.1.tar.gz ]]
Ensure the integrity of your download by checking this source code
archive's cryptographic signature; see "Obtaining groff" below.
What is groff?
==============
groff (GNU roff) is a typesetting system that reads plain text input
that includes formatting commands to produce output in PostScript,
PDF, HTML, or DVI formats or for display to a terminal. Formatting
commands can be low-level typesetting primitives, macros from a
supplied package, or user-defined macros. All three approaches can be
combined.
A reimplementation and extension of troff and other programs from AT&T
Unix, groff is widely available on POSIX and other systems owing to its
long association with Unix manuals, including man pages. It and its
predecessor have produced several best-selling software engineering
texts. groff can create typographically sophisticated documents while
consuming minimal system resources.
https://www.gnu.org/software/groff/
Changes
=======
This release corrects bugs in the groff 1.24.0 release that regressed
working 1.23.0 features, adds automated test scripts, revises unclear or
misleading diagnostic messages, and improves documentation. There are
no new features.
Details
-------
Since groff 1.24.0 was released on 28 February 2026, 3 people have
authored a total of 60 commits.
$ git shortlog --summary 1.24.0..1.24.1
2 Deri James
57 G. Branden Robinson
1 Rocket Ma
The most noteworthy of the foregoing commits are as follows.
f9420c7b0 tmac/troffrc: Fix misleading diagnostic message.
ba0908298 [troff]: Improve error diagnostic.
c71b99984 Use sequential tag names to avoid possible random duplicates.
9c4e2c8c6 [troff]: Fix Savannah #68132.
45afde2cb [troff]: Regression-test Savannah #68132.
37f0060be groff(7): Document `.S` register as reserved.
b9d07e0cf eqn(1): Add "roff interface" subsection.
eee74c1a8 [eqn]: Fix Savannah #68115.
6e467c234 [eqn]: Regression-test Savannah #68115.
Another way of capturing the amount of revision is as follows.
$ git diff --stat 1.24.0 1.24.1 | tail -n 1
87 files changed, 784 insertions(+), 282 deletions(-)
Obtaining groff
===============
Here are the compressed sources and a GPG detached signature[*].
https://ftp.gnu.org/gnu/groff/groff-1.24.1.tar.gz
https://ftp.gnu.org/gnu/groff/groff-1.24.1.tar.gz.sig
Use a mirror for higher download bandwidth.
https://ftpmirror.gnu.org/groff/groff-1.24.1.tar.gz
https://ftpmirror.gnu.org/groff/groff-1.24.1.tar.gz.sig
Here are the SHA-1 and SHA-256 checksums.
6bba283f8b55b74bbcafd56653876ec5d567de63 groff-1.24.1.tar.gz
dOKBl5W2r/QxrqyYPWOpyJaO6roqLrp9+LpMe0Hnz9g= groff-1.24.1.tar.gz
The SHA-256 checksum is encoded in Base64 instead of the hexadecimal
form that most checksum tools default to. The mechanism follows.
sha256sum < groff-1.24.1.tar.gz | cut -f1 -d\ | xxd -r -p | base64
(Because "base64" reads from a pipe, it doesn't know the file name, and
so the file name will not appear in the output.)
[*] Use a .sig file to verify that the corresponding file (without the
.sig suffix) is intact. First, be sure to download both the .sig
file and the corresponding archive. Then, verify the archive.
gpg --verify groff-1.24.1.tar.gz{.sig,}
If that command fails because you don't have the required public
key, you can import it.
wget -O 108747.asc \
'https://savannah.gnu.org/people/viewgpg.php?user_id=108747'
gpg --import 108747.asc
Re-run the 'gpg --verify' command above again subsequently.
Caveats
=======
o GNU tools, or otherwise POSIX-conforming ones, are generally required
to build on Solaris 10 or 11. See the "PROBLEMS" file in the
distribution archive.
o Solaris 10 has known problems with automated tests; see the "PROBLEMS"
file in the distribution archive.
Acknowledgements
================
We'd like to thank the following people for helping ensure the quality
of this release.
Bjarni Ingi Gislason
Clem Cole
Dave Kemper
Peng Zhang
Rocket Ma
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2026-03-14 19:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260314193005.v3rbph3hcks2oltm@illithid \
--to=g.branden.robinson@gmail.com \
--cc=groff@gnu.org \
--cc=info-gnu@gnu.org \
--cc=info-groff@gnu.org \
--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