From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: Deri James <deri@chuzzlewit.myzen.co.uk>, linux-man@vger.kernel.org
Subject: Re: Linux man-pages PDF book
Date: Sun, 14 Apr 2024 08:00:04 -0500 [thread overview]
Message-ID: <20240414130004.23vb7popijc4fac7@illithid> (raw)
In-Reply-To: <ZhvPTME5eU13GlBI@debian>
[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]
Hi Alex,
At 2024-04-14T14:42:51+0200, Alejandro Colomar wrote:
> On Sun, Apr 14, 2024 at 02:32:25PM +0200, Alejandro Colomar wrote:
> > > groff_man(7):
> > > -rC1 Number output pages consecutively, in strictly increasing
> > > sequence, rather than resetting the page number to 1 (or
> > > the value of register P) with each new man document.
> >
> > Hmmmm. Maybe I should follow v7's tradition and restart the page
> > number at each TH. Let's call it an accidental improvement, and not
> > a regression. :)
> >
> > Although it would be interesting to learn when/why this changed.
>
> It seems to have been here:
[...]
> - | troff -Tpdf -dPDF.EXPORT=1 -dLABEL.REFS=1 -dpaper=a4 \
> - -M"$(dirname "$0")" -mandoc -manmark -rC1 -rCHECKSTYLE=3 \
> - 2>&1 >/dev/null \
> - | LC_ALL=C grep '^\. *ds ';
> -
> + cat "$(dirname "$0")"/LMBfront.roff;
> + cat "$(dirname "$0")"/an.tmac;
> "$(dirname "$0")"/prepare.pl "$1";
I don't think there's one right choice here. I _would_ make sure that
the PDF page numbering (visible in the PDF viewer's outline pane)
matches that used by the document. To do otherwise will frustrate
users.
Regards,
Branden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-04-14 13:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-14 11:37 Linux man-pages PDF book Alejandro Colomar
2024-04-14 11:41 ` Alejandro Colomar
2024-04-14 12:01 ` G. Branden Robinson
2024-04-14 12:25 ` Alejandro Colomar
[not found] ` <3935722.768hzMJKAL@pip>
2024-04-16 1:02 ` Alejandro Colomar
2024-04-16 2:08 ` G. Branden Robinson
2024-04-16 2:42 ` Alejandro Colomar
[not found] ` <44896690.SEQk1G1hEZ@pip>
[not found] ` <20240416165157.ml3ntjoozh3mpyzo@illithid>
2024-04-16 20:15 ` Alejandro Colomar
2024-04-16 20:57 ` Alejandro Colomar
2024-04-16 23:17 ` Deri
2024-04-17 9:54 ` Alejandro Colomar
2024-04-17 9:56 ` Alejandro Colomar
2024-04-17 10:28 ` Deri
2024-04-17 10:33 ` Alejandro Colomar
2024-04-17 20:01 ` Deri
2024-04-17 20:48 ` Alejandro Colomar
2024-04-18 0:26 ` Deri
2024-04-18 1:09 ` Alejandro Colomar
2024-04-18 14:45 ` Deri
2024-04-18 0:44 ` Alejandro Colomar
2024-04-18 1:08 ` Alejandro Colomar
2024-04-14 11:57 ` G. Branden Robinson
2024-04-14 12:32 ` Alejandro Colomar
2024-04-14 12:42 ` Alejandro Colomar
2024-04-14 13:00 ` G. Branden Robinson [this message]
2024-04-14 12:56 ` G. Branden Robinson
2024-04-14 15:58 ` Alejandro Colomar
2024-04-14 19:55 ` Alejandro Colomar
2024-04-14 20:25 ` G. Branden Robinson
2024-04-14 21:06 ` Alejandro Colomar
2024-04-14 14:50 ` 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=20240414130004.23vb7popijc4fac7@illithid \
--to=g.branden.robinson@gmail.com \
--cc=alx@kernel.org \
--cc=deri@chuzzlewit.myzen.co.uk \
--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