From: elaexuotee--- via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 40558@debbugs.gnu.org
Subject: bug#40558: Modular TexLive "Insufficient extension fonts" and duplicate fonts
Date: Sat, 22 Jan 2022 08:42:27 +0900 [thread overview]
Message-ID: <321HNQCQ83DRR.3A7ZBRV3CBQ8S@wilsonb.com> (raw)
In-Reply-To: <87sfthovg2.fsf@elephly.net>
Ricardo Wurmus <rekado@elephly.net> wrote:
>
> elaexuotee@wilsonb.com writes:
>
> > Ricardo Wurmus <rekado@elephly.net> wrote:
> >> This is a problem with the modular TeX Live packages. The pk files are
> >> bitmap fonts. I found that adding texlive-cm-super to the union helps
> >> in that the bitmap variants of the CM fonts will not be generated any
> >> more. More font packages may be needed in the union to prevent TeX from
> >> falling back to bitmap fonts in other cases.
> >>
> >> In any case, that’s unrelated to Jelle’s patch, which looks fine to me.
> >
> > Thank you, Ricardo, for looking into this.
> >
> > I have lost signficant amounts of hair trying to find a solution. Adding
> > texlive-cm-super doesn't help for the document I trying to typeset. In fact, I
> > even grabbed all texlive packages with fonts and threw them in the
> > texlive-union to no effect. No matter what, pdflatex bails when trying to find
> > the font to set $~$.
> >
> > The only way I have gotten it to typeset under a texlive-union so far is by
> > munging texlive-amsfonts as Jelle mentioned.
>
> I have since added texlive-amsfonts/fixed, which installs all the files
> it is supposed to (according do the tlpdb). I’ve also since fixed font
> search.
>
> Can this issue be closed?
Are we sure this is fixed? The issue where you added texlive-amsfonts/fixed is
still seeing the original missing fonts error for eufm10:
https://issues.guix.gnu.org/53339#3-lineno36
next prev parent reply other threads:[~2022-01-21 23:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 16:15 bug#40558: Modular TexLive "Insufficient extension fonts" and duplicate fonts Jelle Licht
2020-04-20 19:31 ` Jelle Licht
2022-02-11 19:39 ` Ricardo Wurmus
2020-05-09 10:47 ` bug#40558: (no subject) elaexuotee
2020-05-12 12:36 ` Jelle Licht
2020-10-26 22:10 ` Ricardo Wurmus
2021-02-03 9:57 ` elaexuotee--- via Bug reports for GNU Guix
2022-01-21 17:21 ` bug#40558: Modular TexLive "Insufficient extension fonts" and duplicate fonts Ricardo Wurmus
2022-01-21 23:42 ` elaexuotee--- via Bug reports for GNU Guix [this message]
2022-01-22 7:50 ` Ricardo Wurmus
2022-01-23 2:53 ` elaexuotee--- via Bug reports for GNU Guix
2022-01-23 10:55 ` Ricardo Wurmus
2022-02-11 14:58 ` zimoun
2022-02-15 16:34 ` 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=321HNQCQ83DRR.3A7ZBRV3CBQ8S@wilsonb.com \
--to=bug-guix@gnu.org \
--cc=40558@debbugs.gnu.org \
--cc=elaexuotee@wilsonb.com \
--cc=rekado@elephly.net \
/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).