From: Ricardo Wurmus <rekado@elephly.net>
To: TK <tkprom@protonmail.com>
Cc: help-guix@gnu.org
Subject: Re: Missing LaTeX font (R related)
Date: Tue, 29 Mar 2022 12:57:35 +0200 [thread overview]
Message-ID: <87ilrx81ji.fsf@elephly.net> (raw)
In-Reply-To: <Q_6xkLlp6GJW8xDBU949n6y0vR4k-XdZkeV1o8vBsPgZjVV0zEAOlyyFl8XN5-O-aNmdgMW3zi-g5rVg7_2VXXZlIV5PrEx3FQiarDvv2OY=@protonmail.com>
TK <tkprom@protonmail.com> writes:
> After some more investigation, I think I narrowed down the
> issue. Package texlive-inconsolata indeed installs the `t1-zi4r-0'
> font. However, the `map' for that font exists only under dvips, not in
> the pdftex subdir.
We’re generating these map files based on the contents of the profile.
We’re using a profile hook for this.
> I am not a TeX magus, but it is indicative that the file on the
> official TeXLive repo
> https://tug.org/svn/texlive/trunk/Master/texmf-dist/fonts/map/pdftex/updmap/pdftex.map
> does contain `zi4' entries.
We don’t use that file because it contains *everything*; instead we
generate it in a profile hook so that it only contains entries that
correspond to what has actually been installed.
> Shouldn't the installation of texlive-inconsolata put the
> corresponding entries into `pdftex.map'?
Yes, it should.
> Any hints on where to go from here?
When I do
guix shell -C texlive-base texlive-inconsolata
I see that
$GUIX_ENVIRONMENT/share/texmf-dist/fonts/map/pdftex/updmap/pdftex.map
contains entries for the inconsolata fonts.
(The profile hook depends on texlive-base.)
--
Ricardo
next prev parent reply other threads:[~2022-03-29 11:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 8:45 Missing LaTeX font (R related) TK
2022-03-23 8:58 ` Ricardo Wurmus
2022-03-23 10:02 ` TK
2022-03-29 10:02 ` TK
2022-03-29 10:57 ` Ricardo Wurmus [this message]
2022-03-30 6:55 ` TK
2022-03-30 7:08 ` TK
2022-03-29 10:22 ` Todor Kondić
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=87ilrx81ji.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=tkprom@protonmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.