This is the normal behavior. Latin Modern comes packaged in LaTeX itself. If you need a different font, you can customize your own docker image based on the pandoc/latex image and install the appropriate package (installing packages at runtime has not worked for me), or use --pdf-engine=xelatex and map your fonts directory as a volume onto the docker container. In the latter case, you can no longer use the `uses:` syntax in GitHub Actions, but have to declare it with `run:`.Em quarta-feira, 30 de junho de 2021 às 05:11:25 UTC+1, Shakrmaker escreveu:Well, when I tried Elham my GitHub action run failed on the font, and when I check these in the factory local docker/latex 2.14.0.3 image, I seem to be coming up empty:
# ls /usr/share/fonts
ls: /usr/share/fonts: No such file or directory
# ls /usr/local/share/fonts
ls: /usr/local/share/fonts: No such file or directory
# ls ~./fonts
ls: ~./fonts: No such file or directory
# fc-list
#
The interesting thing to a newbie like me - is where is pandoc getting its default Latin Modern from the docker/latex image? Since the docs say for this latex variable:
https://pandoc.org/MANUAL.html#variables-for-latex > Fonts:
"fontfamily font package for use with pdflatex: The default is Latin Modern."On Tuesday, June 29, 2021 at 11:50:21 PM UTC-4 Shakrmaker wrote:Well, if I'm doing this correctly... when I spin up the 2.14.0.3 docker/latex image and poke around, in:
/usr/share/fontconfig/conf.avail/
I see in: 40-nonlatin.conf:
<!--
Sans-serif faces
-->
<alias>
<family>Arshia</family>
<default><family>sans-serif</family></default>
</alias>
<alias>
<family>Elham</family>
<default><family>sans-serif</family></default>
</alias>...and a continued long list of sans serif ^ font family entries.
Does this mean they're available as a GitHub Action arg with -V fontfamily=Elham, etc? I will try that out next.