From: Christian Franke <Christian.Franke@t-online.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: groff-1.23.0-1
Date: Sat, 22 Jul 2023 23:27:14 +0200 [thread overview]
Message-ID: <128e9daf-448c-ce0f-4eac-4fc76756657d@t-online.de> (raw)
In-Reply-To: <announce.87351nsr2f.fsf@Rainer.invalid>
ASSI via Cygwin wrote:
> GNU roff has been updated to the latest upstream version 1.23.0. The
> following packages are available on Cygwin:
>
> groff-1.23.0-1
> groff-perl-1.23.0-1
> groff-X11-1.23.0-1
>
- Various PDF fonts produce warnings but seem to work in general:
$ echo "Hello, World!" | groff -Tpdf -f A > hello.A.pdf
/usr/bin/gropdf: warning: The download file in
'/usr/share/groff/1.23.0/font/devpdf' has erroneous entry for
'AvantGarde-Book (AR)'
$ grep -a BaseFont hello.A.pdf
5 0 obj << /BaseFont /AvantGarde-Book
Affected are all except T(imes), H(elvetica) and C(ourier).
This script tests all PDF fonts for warnings:
===
#!/bin/sh
(cd /usr/share/groff/current/font/devpdf && ls -d *R 2>/dev/null) \
| while read f; do
f=${f%R}
echo "$f:"
echo "Hello, World!" | groff -Tpdf -f "$f" > "hello.$f.pdf"
done
===
- Man pages could no longer be formatted with a specific font. Only
header and footer lines use the selected font then, the rest stays at
the default font 'T':
$ zcat /usr/share/man/man1/ls.1.gz | groff -man -Tpdf -f H > ls.1.H.pdf
$ grep -a BaseFont ls.1.H.pdf
6 0 obj << /BaseFont /Helvetica-Oblique
10 0 obj << /BaseFont /Helvetica
13 0 obj << /BaseFont /Times-Bold
16 0 obj << /BaseFont /Times-Roman
19 0 obj << /BaseFont /Times-Italic
Intentional change or regression?
--
Regards,
Christian
next prev parent reply other threads:[~2023-07-22 21:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 17:29 ASSI
2023-07-22 21:27 ` Christian Franke [this message]
2023-07-23 1:35 ` Brian Inglis
2023-07-23 11:08 ` ASSI
2023-07-23 13:55 ` Christian Franke
2023-07-23 14:52 ` Christian Franke
2023-07-23 15:35 ` ASSI
2023-07-23 15:34 ` ASSI
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=128e9daf-448c-ce0f-4eac-4fc76756657d@t-online.de \
--to=christian.franke@t-online.de \
--cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).