From: "Wiktor Żelazny" <wz@freeshell.de>
To: help-guix@gnu.org
Subject: XeLaTeX, fontspec, unsuccessful font search
Date: Wed, 22 Jan 2020 16:25:43 +0100 [thread overview]
Message-ID: <20200122152543.xjb6qvbvjsbkeuxo@wzguix> (raw)
[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]
Dear list,
I’ve been tackling a similar problem as in [1]:
$ cat minimal.tex
\documentclass{minimal}
\usepackage{fontspec}
\setmainfont{Latin Modern Sans}
\begin{document}
Hello
\end{document}
$ guix environment --container --ad-hoc texlive texlive-latex-fontspec texlive-lm
[env]$ xelatex minimal
(/gnu/store/ar2lrskw5mbqyc8k7ai3i7p5ig6fdkp0-texlive-texmf-20180414/share/texmf
-dist/tex/latex/fontspec/fontspec.cfg)))kpathsea:make_tex: Invalid filename `Latin Modern Sans', contains ' '
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
! fontspec error: "font-not-found"
!
! The font "Latin Modern Sans" cannot be found.
!
! See the fontspec documentation for further information.
!
! For immediate help type H <return>.
!...............................................
l.3 \setmainfont{Latin Modern Sans}
Actually, it started with me trying to obtain a pdf output with `pandoc
--pdf-engine=xelatex` from a markdown file. This returns a different
error, albeit seemingly related: lmodern not found. So the issue looks
deeper than the space in the font name.
For an environment without `--container`, `fc-match` returns no match,
even after `fc-cache -f`.
Any hint will be appreciated.
WŻ
[1]: https://github.com/NixOS/nixpkgs/issues/24485
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next reply other threads:[~2020-01-22 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 15:25 Wiktor Żelazny [this message]
2020-01-23 14:11 ` XeLaTeX, fontspec, unsuccessful font search Wiktor Żelazny
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=20200122152543.xjb6qvbvjsbkeuxo@wzguix \
--to=wz@freeshell.de \
--cc=help-guix@gnu.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 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.