From: Terence Eden <terence.eden-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Bug with fonts in subdirectory?
Date: Sun, 13 Nov 2022 05:55:34 -0800 (PST) [thread overview]
Message-ID: <62aceeb4-46d0-4079-9c5b-1be3dd5e2bben@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1375 bytes --]
I am trying to convert a .md file to a .pdf using a specific TTF font.
Pandoc doesn't work unless the .ttf is in the same directory as the .md
file. Is that normal?
This works:
pandoc in.md --pdf-engine=xelatex -V mainfont="font.ttf" -o test.pdf
I get a PDF in my specific font.
But this fails:
pandoc in.md --pdf-engine=xelatex -V mainfont="fonts/fontname/font.ttf" -o
test.pdf
It gives the error:
Error producing PDF.
! Missing number, treated as zero.
<to be read again>
f
l.19 \fi
I know Pandoc can read the directory, because if I try to use a .ttf which
doesn't exist, I get the error "! Package fontspec Error: The font
"fonts/foo/bar" cannot be found."
Is this a bug, or me not understanding how to use Pandoc properly (a
distinct possibility!)
Thanks
pandoc 2.19.2
Compiled with pandoc-types 1.22.2.1, texmath 0.12.5.2, skylighting 0.13,
citeproc 0.8.0.1, ipynb 0.2, hslua 2.2.1
Scripting engine: Lua 5.4
Ubuntu: 22.04
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/62aceeb4-46d0-4079-9c5b-1be3dd5e2bben%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2012 bytes --]
next reply other threads:[~2022-11-13 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 13:55 Terence Eden [this message]
[not found] ` <62aceeb4-46d0-4079-9c5b-1be3dd5e2bben-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-13 15:32 ` Joost Kremers
[not found] ` <87zgcuhnl8.fsf-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2022-11-13 16:14 ` Terence Eden
[not found] ` <cd84e8c7-0bc4-4828-a090-12e7c679cf1fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-13 17:40 ` Bastien DUMONT
2022-11-13 19:29 ` Joost Kremers
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=62aceeb4-46d0-4079-9c5b-1be3dd5e2bben@googlegroups.com \
--to=terence.eden-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).