public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org, Deri James <deri@chuzzlewit.myzen.co.uk>
Subject: Re: man-pages PDF book: fonts
Date: Mon, 25 Mar 2024 13:07:38 +0100	[thread overview]
Message-ID: <ZgFpCkCcwxMzsOcw@debian> (raw)
In-Reply-To: <ZgFioIO94vFupB53@debian>

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

Hi Branden,

On Mon, Mar 25, 2024 at 12:40:07PM +0100, Alejandro Colomar wrote:
> > The grops(1) and gropdf(1) man pages in groff 1.23.0 discuss using this
> > tool to prepare fonts so that groff can read them.
> 
> Hmmm, so I could add a Makefile target to produce this .pfa font from
> the packaged .pfb one, and then get gropdf(1) to use this one.  --Using
> a Makefile pays for itself.--  The process is fast, it seems.
> 
> $ time pfbtops \
> 	/usr/share/texlive/texmf-dist/fonts/type1/google/tinos/Tinos.pfb \
> | wc -l
> 19570
> 
> real	0m0.012s
> user	0m0.015s
> sys	0m0.001s
> 
> I'll try it.  This should remove a gigantic file from the project
> repository.  Thanks!  =)

I'm a bit worried that with the font regenerated from the packaged one
and pfbtops(1) I get a lot more warnings.  The PDF still seems okay at
first glance, but I'm not sure if there's something wrong with what I'm
doing:


$ pfbtops \
	/usr/share/texlive/texmf-dist/fonts/type1/google/tinos/Tinos.pfb \
	>scripts/LinuxManBook/devpdf/Tinos.pfa ;
$ make build-man -j24 >/dev/null;
$ make build-pdf-book |& wc -l;
1349
$ git stash;
Saved working directory and index state WIP on contrib: 49e6388bb share/mk/: srcfix
$ rm .tmp/man-pages-*.pdf;
$ make build-pdf-book |& wc -l;
260


Maybe I also need to regenerate the TINOR file?  And how do I regenerate
that one, and what's its source?

Cheers,
Alex

-- 
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.

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

  parent reply	other threads:[~2024-03-25 12:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-22 17:35 man-pages PDF book: fonts Alejandro Colomar
2024-03-25  4:19 ` G. Branden Robinson
2024-03-25 11:40   ` Alejandro Colomar
2024-03-25 11:48     ` Alejandro Colomar
2024-03-25 12:07     ` Alejandro Colomar [this message]
2024-03-25 18:36   ` James Cloos
2024-03-26 18:10   ` Brian Inglis
2024-04-20 12:06     ` Alejandro Colomar
2024-04-20 13:00       ` 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=ZgFpCkCcwxMzsOcw@debian \
    --to=alx@kernel.org \
    --cc=deri@chuzzlewit.myzen.co.uk \
    --cc=g.branden.robinson@gmail.com \
    --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