From: BPJ <melroch-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: Wed, 7 Jul 2021 09:21:38 +0200 [thread overview]
Message-ID: <CADAJKhCyYv67UAEBG4fWr_MbETy3mQ1gCuyG57G=5OT9btUDpw@mail.gmail.com> (raw)
In-Reply-To: <e14acfcd-b5da-42ef-9261-fc5a0ab0953bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 3444 bytes --]
Reading the relevant parts of the manual should clear things up:
https://pandoc.org/MANUAL.html#option--defaults
https://pandoc.org/MANUAL.html#default-files
I always use XeLaTeX but I think that fontfamily should go in the metadata
section of a defaults file:
``````yaml
metadata:
fontfamily: whatever
fontfamilyoptions:
- 'option=value'
``````
Using XeLaTeX (`pdf-engine: xelatex` in a defaults file or
`--pdf-engine=xelatex` on the command line) along with `mainfont:
Helvetica` would probably solve your problem instantly provided the system
in your docker image has this font installed (or you might install Noto
Sans as a very good alternative if a free Helvetica OTF/TTF version isn't
available). However XeLaTeX is considerably slower than pdfLaTeX which may
matter if you are serving this live.
Den tis 6 juli 2021 23:51Shakr Maker <shakrmaker-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> skrev:
> Hi John, Pedro,
>
> Where (in what file) are you defining this yaml when you get your
> Helvetica result? Are you adding this yaml to your .md file? Or some other
> file? How are you calling it and with what arg?
> ---
> fontfamily: helvet
> ...
>
> I've tried passing it in as *-d* (which it apparently isn't, based on
> https://pandoc.org/MANUAL.html#default-files)
> I've tried using *--metadata-file* (which it perhaps isn't and appears to
> ignore https://pandoc.org/MANUAL.html#option--metadata-file)
> I've tried passing it in as a sequential yaml file per (
> https://pandoc.org/MANUAL.html#extension-yaml_metadata_block)
> And I earlier tried the straight argument without the yaml, *-V
> fontfamily=helvet*
>
> None of them work. I still don't get Helvetica.
>
> Thanks for any help!
>
>
>
> On Thursday, July 1, 2021 at 11:56:24 AM UTC-4 John MacFarlane wrote:
>
>>
>> I do get Helvetica font when I try this (pandoc test.md -o test.pdf).
>>
>> "Pedro P. Palazzo" <pedro....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>
>> > OK, there's something weird going on with Pandoc (not the Docker
>> image). I created a test file with the following in the front matter:
>> >
>> > ---
>> > fontfamily: helvet
>> > header-includes:
>> > - \renewcommand\familydefault{\sfdefault}
>> > ---
>> >
>> > If I run `pandoc -o myfile.pdf`, it does NOT use Helvetica. However, if
>> I run `pandoc -o myfile.tex` and then `pdflatex myfile`, the document DOES
>> come out in Helvetica. Not sure where to go from here, though.
>>
>> --
> 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/e14acfcd-b5da-42ef-9261-fc5a0ab0953bn%40googlegroups.com
> <https://groups.google.com/d/msgid/pandoc-discuss/e14acfcd-b5da-42ef-9261-fc5a0ab0953bn%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
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/CADAJKhCyYv67UAEBG4fWr_MbETy3mQ1gCuyG57G%3D5OT9btUDpw%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 5554 bytes --]
next prev parent reply other threads:[~2021-07-07 7:21 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 [this message]
[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
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='CADAJKhCyYv67UAEBG4fWr_MbETy3mQ1gCuyG57G=5OT9btUDpw@mail.gmail.com' \
--to=melroch-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).