From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Cc: "Eugenio López Cortegano"
<elcortegano-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: Xelatex report missing libraries, or fails at using fonts
Date: Fri, 14 Jan 2022 09:03:39 +0100 [thread overview]
Message-ID: <87y23ivj4i.fsf@zeitkraut.de> (raw)
In-Reply-To: <253c9e22-d112-46d7-94cf-dee1dc7e697fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Hi Eugenio,
If it worked before but stopped working, then that's probably due to the
changes mentioned here:
https://groups.google.com/g/pandoc-discuss/c/aj4mrQc5nuQ/m/bh_ALPp8AgAJ
We reduced the number of packages that ship with that image.
The recommended solution is to build your own Docker image locally. For
that you'll need a file `Dockerfile` with the following content:
``` dockerfile
FROM pandoc/latex:2.17-alpine
# Install fonts via the Alpine package manager.
# Here we install 'Hack', a monotype font with support for many
# unicode chars.
RUN apk add --no-cache ttf-hack
# Install additional LaTeX packages. List all the one you need.
RUN tlmgr update --self && tlmgr install \
enumitem \
tcolorbox
```
Then run something like `docker build --tag myimage .` to build the
image and use it instead of pandoc/latex.
Let us know if the other issues persist when using the above method.
Cheers,
Albert
--
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
next prev parent reply other threads:[~2022-01-14 8:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 22:32 Eugenio López Cortegano
[not found] ` <253c9e22-d112-46d7-94cf-dee1dc7e697fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-01-14 8:03 ` Albert Krewinkel [this message]
[not found] ` <87y23ivj4i.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-01-14 11:52 ` BPJ
[not found] ` <CADAJKhAsgjcLopjrdx0Zx2K4snc1dRLNorVAkAUJLzTWm4Jhfw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-01-14 13:27 ` Eugenio López Cortegano
[not found] ` <CAGjgynYsn=NVM_1kvxTVSp0T5KJxQiTW94y6Z9aTYUPXppy4Xg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-01-14 19:38 ` Eugenio López Cortegano
[not found] ` <CAGjgynaW43_MqU4Dna7=0krg8a=zBPDHT-eBNZdo6FZGt=Mr_A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-01-15 13:40 ` Albert Krewinkel
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=87y23ivj4i.fsf@zeitkraut.de \
--to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@public.gmane.org \
--cc=elcortegano-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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 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 NNTP newsgroup(s).