From: Deri <deri@chuzzlewit.myzen.co.uk>
To: Alejandro Colomar <alx@kernel.org>
Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
linux-man@vger.kernel.org
Subject: Re: Linux man-pages PDF book
Date: Wed, 17 Apr 2024 00:17:18 +0100 [thread overview]
Message-ID: <4499122.GHtaDqYCYT@pip> (raw)
In-Reply-To: <Zh7mRYSj-st4i0z-@debian>
[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]
On Tuesday, 16 April 2024 21:57:41 BST Alejandro Colomar wrote:
> I've moved it to .../devpdf and
> added the download file, and it still doesn't work.
Hi Alex,
What was not clear when I wrote:-
"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."
But instead you changed _FONTSDIR to point to devpdf.
The difference in the pages between having working and non-working fonts is
seen in the attached example pages (compare with your book). These in fact are
using UnifontM. TINOR provides the cyrillic glyphs and greek of the iso_8859
pages if I remember.
You can still see some gaps (which should not happen using UnifontM) they
appear to be caused by an issue in one of Branden's commits, see:-
https://savannah.gnu.org/bugs/?65601
Cheers
Deri
[-- Attachment #2: LMB-working-fonts.pdf --]
[-- Type: application/pdf, Size: 122654 bytes --]
next prev parent reply other threads:[~2024-04-16 23:33 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
[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 [this message]
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=4499122.GHtaDqYCYT@pip \
--to=deri@chuzzlewit.myzen.co.uk \
--cc=alx@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.