From: Shakr Maker <shakrmaker-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Available default fonts in a factory pandoc/latex Docker image?
Date: Tue, 6 Jul 2021 08:56:30 -0700 (PDT) [thread overview]
Message-ID: <fd6c8b85-3f2b-4b27-96c0-dd6da496b7a5n@googlegroups.com> (raw)
In-Reply-To: <1e628991-6606-4d72-80c9-7489b9d08518n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1186 bytes --]
I've tried which I believe is your guys' way; using front matter via *-d
FILE* per
https://pandoc.org/MANUAL.html#general-options
When I use that argument below with a valid data file that pandoc finds, in
the GitHub Action run with my custom Docker image
<https://hub.docker.com/repository/docker/tojdk/pandoc-latex-fonts> (note:
which again.. is just the generic pandoc 2.14.0.3 docker image with tlmgr
install collection-fontsrecommended applied to it and using default latex
converter):
-d pandoc-pdf-config.yaml
Whose file file contents above ^ contains just this:
---
fontfamily: helvet
...
I get this in the run:
Error parsing pandoc-pdf-config.yaml line 2 column 0:
Unknown option "fontfamily"
Thoughts? Am I doing something wrong?
Thanks for any help!
--
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/fd6c8b85-3f2b-4b27-96c0-dd6da496b7a5n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1903 bytes --]
next prev parent reply other threads:[~2021-07-06 15:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 22:44 Shakrmaker
[not found] ` <bb821641-7fc9-420f-907f-36d198800d84n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-06-30 3:50 ` Shakrmaker
[not found] ` <8a071f76-add3-4917-aa67-6fd73402d3f6n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-06-30 4:11 ` Shakrmaker
[not found] ` <1d9e9bc2-6820-4b57-9729-ef7c170cbd43n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-06-30 11:07 ` Pedro P. Palazzo
[not found] ` <dbe68bc0-6b51-4c28-81ac-ae4c3e4d8743n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-06-30 19:10 ` Shakrmaker
[not found] ` <4ed25c3b-269a-4564-8eb5-42de0c7c0202n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-06-30 23:34 ` Shakrmaker
[not found] ` <58a94bbf-36e1-415f-b928-bb0abcf4f9c6n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-07-01 2:22 ` Shakrmaker
[not found] ` <f6a86403-c99d-41b3-8568-c4f6aef23812n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-07-01 13:52 ` Pedro P. Palazzo
[not found] ` <A2E180F9-B20C-416D-BFB8-59139ACEB020-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2021-07-01 15:56 ` John MacFarlane
[not found] ` <m24kdejaee.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2021-07-06 21:51 ` Shakr Maker
[not found] ` <e14acfcd-b5da-42ef-9261-fc5a0ab0953bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-07-07 7:21 ` BPJ
[not found] ` <CADAJKhCyYv67UAEBG4fWr_MbETy3mQ1gCuyG57G=5OT9btUDpw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-07-07 21:16 ` Shakr Maker
2021-07-01 20:37 ` Shakrmaker
[not found] ` <1e628991-6606-4d72-80c9-7489b9d08518n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-07-06 15:56 ` Shakr Maker [this message]
2021-07-07 22:05 ` Pedro P. Palazzo
[not found] ` <3c5dc4f1-2030-45a0-abb3-387bfee5014en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-07-08 7:33 ` BPJ
[not found] ` <CADAJKhA2W91wizTEtRu0b7QsYnMUFbMtj9y8akhK8uvy=sq4JA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-07-08 13:50 ` Shakr Maker
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=fd6c8b85-3f2b-4b27-96c0-dd6da496b7a5n@googlegroups.com \
--to=shakrmaker-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).