unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Jelle Licht <jlicht@fsfe.org>
Cc: 52979@debbugs.gnu.org
Subject: bug#52979: Modular texlive has problems finding fonts
Date: Tue, 04 Jan 2022 10:19:29 +0100	[thread overview]
Message-ID: <87v8yzestw.fsf@elephly.net> (raw)
In-Reply-To: <87zgocdjkl.fsf@elephly.net>


Ricardo Wurmus <rekado@elephly.net> writes:

> Jelle Licht <jlicht@fsfe.org> writes:
>
>> We can disable this optimisation by setting ST_NLINK_TRICK at compile
>> time.
>
> That’s what I did, and it does let kpathsea traverse all the fonts.
> Unfortunately, in my tests it does not fix pdflatex.  It does, however,
> fix xelatex.
>
> Debbugging output suggests that pdflatex encounters the font file
> cmr10.tfm, but for some unknown reason doesn’t seem to be satisfied with
> it.

It finds cmr10.tfm and then later proceeds to search (with
“must_exist=1”) for bitmap fonts such as dpi656/cmr10.pk (cmr10.656pk)
or dpi659/cmr10.pk (cmr10.659pk).

That’s how it fails:

  !pdfTeX error: pdflatex (file cmr10): Font cmr10 at 657 not found

657 is the resolution.  The other sizes are due to
KPSE_BITMAP_TOLERANCE; it will also search for alternatives whose
resolution is close enough to the intended size.

I wonder why it bothers with bitmap fonts at all.  And why it looks for
this really odd resolution.  We have
texmf-dist/fonts/pk/ljfour/public/cm/dpi600/cmr10.pk.  Why doesn’t it
look for a font with resolution 600?  The resolution 657 must have been
computed somewhere.

-- 
Ricardo




  reply	other threads:[~2022-01-04  9:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03 16:18 bug#52979: Modular texlive has problems finding fonts Jelle Licht
2022-01-03 17:06 ` Jelle Licht
2022-01-04  7:50   ` Ricardo Wurmus
2022-01-04  9:19     ` Ricardo Wurmus [this message]
2022-01-04  9:58       ` Ricardo Wurmus
2022-01-04 14:28         ` Ricardo Wurmus

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v8yzestw.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=52979@debbugs.gnu.org \
    --cc=jlicht@fsfe.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).