I had trouble with the Microsoft fonts. I'd specified Arial and Courier New, and I can't remember exactly what the problem was (some characters not printing or some such), but was allowed to go back to NotoSans and SourceCodePro, so I didn't give it another thought.

On 2/11/20 9:21 AM, Joost Kremers wrote:

On Tue, Feb 11 2020, tutiluren via pandoc-discuss wrote:
This command WORKS (creates a PDF with the "Arial" font):

    pandoc --pdf-engine=xelatex -V pagestyle="empty" -V     mainfont="Arial" -V monofont="Arial" -V fontsize=10pt     --verbose -V papersize="A4" -V margin-top="2cm" -V     margin-right="2cm" -V margin-bottom="2cm" -V     margin-left="2cm" "test.md" -o "out.pdf"

This command also WORKS (creates a PDF with the "Courier New" font):

    pandoc --pdf-engine=xelatex -V pagestyle="empty" -V     mainfont="Courier New" -V monofont="Courier New" -V     fontsize=10pt --verbose -V papersize="A4" -V     margin-top="2cm" -V margin-right="2cm" -V     margin-bottom="2cm" -V margin-left="2cm" "test.md" -o     "out.pdf"

However, both these commands FAIL (no PDF created at all):

    pandoc --pdf-engine=xelatex -V pagestyle="empty" -V     mainfont="Courier" -V monofont="Courier" -V fontsize=10pt     --verbose -V papersize="A4" -V margin-top="2cm" -V     margin-right="2cm" -V margin-bottom="2cm" -V     margin-left="2cm" "test.md" -o "out.pdf"

    pandoc --pdf-engine=xelatex -V pagestyle="empty" -V     mainfont="Courier Standard" -V monofont="Courier Standard"     -V fontsize=10pt --verbose -V papersize="A4" -V     margin-top="2cm" -V margin-right="2cm" -V     margin-bottom="2cm" -V margin-left="2cm" "test.md" -o     "out.pdf"

From the massive dump of output (containing lots of private paths and stuff), I was able to extract out these clues:

    xdvipdfmx:fatal: This font using the "seac" command for     accented characters...
    No output PDF file written.

What does it mean? What exactly is wrong? In Windows' font dir, there is a "Courier Standard", which, when opened, is simply called "Courier". Both of those strings result in the nonsensical error.

DuckDuckGo is your friend. :-) The info I'm finding on the net is that this indicates the font you're using is a Postscript Type 1 font, which XeTeX doesn't fully support. It should work if you use is a TTF or an OTF font. (The file name should have a `.ttf` or `.otf` file extension. Type 1 fonts will have `.pfb`, `.pfm` or `.afm`, according to Wikipedia.)

Note that the name under which a font is known to the system (and under which XeLaTeX would search for it) is not necessarily identical to the file name of the font on disk. The Windows control panel should have an option to view the fonts installed on your system. (Just quoting what I read online here. I can't check myself because I don't have access to Windows.)

HTH

--
Learn by Doing with Linux Academy Multicloud
                  Training

#1 Learn-by-Doing Multicloud Training Platform



Craig Parker
Technical Writer
Schedule a Meeting or Call


125 Bear Creek Parkway. Keller. Texas 76248

LinuxAcademy.com
Learn faster and deeper with REAL
          Hands-On Labs.



© Linux Academy, 2019. All Rights Reserved.
Pinehead® and the Linux Academy Logo® are registered trademarks of Linux Academy in the U.S. and other countries. Linux® is a registered trademark of Linus Torvalds in the U.S. and other countries.

--
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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/580978a3-ebcb-429d-266e-4c825c61badb%40linuxacademy.com.