public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Deri James <deri@chuzzlewit.myzen.co.uk>
Cc: linux-man@vger.kernel.org
Subject: Linux man-pages PDF book
Date: Sun, 14 Apr 2024 13:37:15 +0200	[thread overview]
Message-ID: <Zhu_-FE5sl3vSu1w@debian> (raw)

[-- Attachment #1: Type: text/plain, Size: 1661 bytes --]

Hi Deri,

Since the conversation in groff's bug report was getting off-topic, I'm
opening this email thread.

The makefile target was recently renamed from build-book to
build-pdf-book (for consistency reasons).

I also reorganized the files to put them inside the build system.  Here
are now the files most relevant for generating the book:

	$ find \
		share/mk/configure/build-depends/texlive-fonts-extra/ \
		share/mk/build/fonts/ \
		share/mk/build/pdf/book/ \
		-type f;
	share/mk/configure/build-depends/texlive-fonts-extra/Tinos.pfb.mk
	share/mk/build/fonts/_.mk
	share/mk/build/fonts/TINOR
	share/mk/build/fonts/tinos.mk
	share/mk/build/pdf/book/_.mk
	share/mk/build/pdf/book/prepare.pl
	share/mk/build/pdf/book/front.roff
	share/mk/build/pdf/book/an.tmac

I removed the Tinos.pfa file, since now I generate it at build time
from the Tinos.pfb file (installed with Debian's texlive-fonts-extra).

Either the reorganization, or the generation of the font results in a
new warning:

troff:<standard input>:1649: error: cannot load font 'TINOR' to mark it as special

Since I didn't notice any changes in the PDF visually, and I removed a
gigantic binary file, I proceeded with it, even with the new warning.
It would be great if we can do something similar to get rid of the TINOR
file, and generate it at build time.
I would also like to do the same with the Unifont font, which I haven't
yet added because I hate adding gigantic binary files to the repo.

There's also the page issue.  Now it seems to reset the page number for
every TH.

Have a lovely day!
Alex

-- 
<https://www.alejandro-colomar.es/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2024-04-14 11:37 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-14 11:37 Alejandro Colomar [this message]
2024-04-14 11:41 ` Linux man-pages PDF book 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
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=Zhu_-FE5sl3vSu1w@debian \
    --to=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