From: Alejandro Colomar <alx@kernel.org>
To: Deri <deri@chuzzlewit.myzen.co.uk>,
linux-man <linux-man@vger.kernel.org>
Cc: Brian Inglis <Brian.Inglis@Shaw.ca>,
"G. Branden Robinson" <g.branden.robinson@gmail.com>,
groff <groff@gnu.org>
Subject: Re: PDF book improvements
Date: Sun, 13 Aug 2023 01:36:30 +0200 [thread overview]
Message-ID: <929cceff-b394-13aa-a3ae-9ef9d1b21ee5@kernel.org> (raw)
In-Reply-To: <3acefa68-2055-1978-da55-cc4f66cdd255@kernel.org>
[-- Attachment #1.1: Type: text/plain, Size: 2405 bytes --]
On 2023-08-12 23:46, Alejandro Colomar wrote:
> Hi Deri,
>
> My end goal is to be able to embed the creation of the PDF book in the
> Makefiles. To that end, as a first step, I'd like to reuse part of
> what we already have in the Makefile. Currently, we process all files
> with -Tpdf, which I guess we'll be able to reuse.
>
> $ make build-pdf -kij >/dev/null 2>&1
> $ touch man2/gettimeofday.2
> $ make build-pdf V=1 | sed '/^[[:upper:]]/s/^/\n/'
>
> PRECONV .tmp/man/man2/gettimeofday.2.tbl
> preconv man2/gettimeofday.2 >.tmp/man/man2/gettimeofday.2.tbl
>
> TBL .tmp/man/man2/gettimeofday.2.eqn
> tbl <.tmp/man/man2/gettimeofday.2.tbl >.tmp/man/man2/gettimeofday.2.eqn
>
> EQN .tmp/man/man2/gettimeofday.2.pdf.troff
> ! (eqn -Tpdf <.tmp/man/man2/gettimeofday.2.eqn 2>&1 >.tmp/man/man2/gettimeofday.2.pdf.troff) \
> | grep ^ >&2
>
> TROFF .tmp/man/man2/gettimeofday.2.pdf.set
> ! (troff -Tpdf -wbreak -man <.tmp/man/man2/gettimeofday.2.pdf.troff 2>&1 >.tmp/man/man2/gettimeofday.2.pdf.set) \
> | grep ^ >&2
>
> GROPDF .tmp/man/man2/gettimeofday.2.pdf
> gropdf <.tmp/man/man2/gettimeofday.2.pdf.set >.tmp/man/man2/gettimeofday.2.pdf
>
> What part of this "pipeline" can we reuse? I guess we can reuse the
> .pdf.troff files. The .pdf.set files probably cannot be reused for
> the single book, as they'll have the page numbers and so on already
> set, right?
>
> So, I'm imagining that we could cat(1) your front cover with all
> these files, and then process with troff(1) and gropdf(1). Does
> that make sense?
>
> Could we also reuse the .pdf.set files and only run gropdf(1) on
> the catenation of them?
I added a script to sort these files, as you do with your sortman()
perl function. I called it sortman too :)
$ cat scripts/sortman
#!/bin/sh
# Copyright 2023, Alejandro Colomar <alx@kernel.org>
# SPDX-License-Identifier: GPL-3.0-or-later
export LC_COLLATE=en_US.UTF-8;
sed -E '/\/intro./ s/.*\.([1-8])$/\10\t&/' \
| sed -E '/\/intro./!s/.*\.([1-8])$/\11\t&/' \
| sed -E '/\/intro./!s/.*\.([1-8].+)/\1\t&/' \
| sort \
| cut -f2;
We'll probably need this to sort the files in the shell.
>
> Cheers,
> Alex
>
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-08-12 23:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 21:46 PDF book improvements Alejandro Colomar
2023-08-12 21:53 ` Alejandro Colomar
2023-08-12 23:36 ` Alejandro Colomar [this message]
2023-08-13 14:34 ` [linux-man book] Fonts from a library (was: PDF book improvements) 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=929cceff-b394-13aa-a3ae-9ef9d1b21ee5@kernel.org \
--to=alx@kernel.org \
--cc=Brian.Inglis@Shaw.ca \
--cc=deri@chuzzlewit.myzen.co.uk \
--cc=g.branden.robinson@gmail.com \
--cc=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