From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Deri <deri@chuzzlewit.myzen.co.uk>, linux-man@vger.kernel.org
Subject: Re: Linux man-pages PDF book
Date: Tue, 16 Apr 2024 04:42:55 +0200 [thread overview]
Message-ID: <Zh3lryFtCbbnUvaV@debian> (raw)
In-Reply-To: <20240416020822.tsrgfu5dr2dlskbr@illithid>
[-- Attachment #1: Type: text/plain, Size: 2130 bytes --]
Hi Branden,
On Mon, Apr 15, 2024 at 09:08:22PM -0500, G. Branden Robinson wrote:
> At 2024-04-16T03:02:28+0200, Alejandro Colomar wrote:
> > > > troff:<standard input>:1649: error: cannot load font 'TINOR' to
> > > > mark it as special
> > >
> > > Your _FONTSDIR must point to a directory which has a subdirectory
> > > called 'devpdf' which holds TINOR and UnifontM and a suitable
> > > 'download' file which gives the location of the actual .pf[ab] files
> > > (i.e. within texlive - no need to copy it). The difference,
> > > with/without, is in the number of glyphs not found messages.
> >
> > I also need to understand what's that TINOR file, what type of file it
> > is, and how I can get it.
>
> This, I can answer. It is a device-independent troff font description
> file. It is a plain text file in a format documented by Brian Kernighan
> originally in CSTR #97 in about 1982, then in the 1992 revision of CSTR
> #54, and of course also in the groff_font(5) man page.
>
> The reason for the font description file is that traditionally digital
> fonts were (1) restrictively licensed and (2) programs that used fonts
> often didn't need the fonts themselves, but just descriptions of what
> glyphs they contained and the dimensions ("metrics") of each glyph. It
> is a rendering device that uses a digital font. A typesetter (or
> graphical display system[1]) needs only to know the metrics of the
> glyphs to that it can position them appropriately relative to each
> other.
>
> This is why when PDF renderers substitute fonts, the result is often so
> terribly ugly. The glyphs of the substituted font are placed in
> positions appropriate to a font that may have different metrics. So
> they are crowded or spaced out weirdly, the kerning is off, and so on.
Thanks. Althoguh this doesn't answer how I can get it in Debian. And
now I also wonder if I really need this file. groff(1) is reporting
warnings that it's not able to use it, and it all still works. Maybe I
don't need it at all?
Have a lovely night!
Alex
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-04-16 2:43 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 [this message]
[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=Zh3lryFtCbbnUvaV@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