From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: Re: man-pages PDF book: fonts
Date: Sun, 24 Mar 2024 23:19:54 -0500 [thread overview]
Message-ID: <20240325041954.fofjtgghwhe4znm6@illithid> (raw)
In-Reply-To: <Zf3BRmfTFvADOIBG@debian>
[-- Attachment #1: Type: text/plain, Size: 2047 bytes --]
Hi Alex,
At 2024-03-22T18:35:02+0100, Alejandro Colomar wrote:
> I see that Debian provides the Tinos font in some package:
>
> $ apt-file find -x Tinos.*pf
> texlive-fonts-extra: /usr/share/texlive/texmf-dist/fonts/type1/google/tinos/Tinos-Bold.pfb
> texlive-fonts-extra: /usr/share/texlive/texmf-dist/fonts/type1/google/tinos/Tinos-BoldItalic.pfb
> texlive-fonts-extra: /usr/share/texlive/texmf-dist/fonts/type1/google/tinos/Tinos-Italic.pfb
> texlive-fonts-extra: /usr/share/texlive/texmf-dist/fonts/type1/google/tinos/Tinos.pfb
>
> The above is .pfb, not .pfa, which I don't understand and may not be
> usable for our purposes,
PFA and PFB are closely related font file formats. Reputedly, they
stand for "PostScript" (or "Printer") "Font" "ASCII" or "Binary",
respectively. PFB was much more widely used on MS-DOS, due either to
the meager disk space there, the 640kB RAM limit, or because it was
thought that the fonts would be "pirated" (or even understood) less
because the nature of their contents was less obvious. Who knows?
Regardless, groff provides a tool for converting uncouth PFB to
civilized PFA.
$ apropos pfbtops
pfbtops (1) - translate Printer Font Binary files to PostScript ASCII
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.
(Why not "pfbtopfa"? Ghostscript was already using that name. Why does
groff provide a tool that does the same thing? Good question. I don't
know. It is not a young program--it is old.[1] Maybe at one time groff
was portable to MS-DOS but Ghostscript was not.)
> Can we similarly get the Unifont for zh_CN PDFs?
As I understand it, GNU Unifont is a low-resolution bitmap font intended
for terminal emulators.[2] I expect it would look offensively bad when
typeset.
Regards,
Branden
[1] https://git.savannah.gnu.org/cgit/groff.git/tree/NEWS?h=1.23.0#n3211
https://www.youtube.com/watch?v=K2tgZCabTzs
[2] https://unifoundry.com/unifont/index.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-03-25 4:19 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 [this message]
2024-03-25 11:40 ` Alejandro Colomar
2024-03-25 11:48 ` Alejandro Colomar
2024-03-25 12:07 ` Alejandro Colomar
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=20240325041954.fofjtgghwhe4znm6@illithid \
--to=g.branden.robinson@gmail.com \
--cc=alx@kernel.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