From: Craig Parker <craigp-UzRat0APdLvLPIzirxu/xA@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Why does Pandoc fail to create a PDF for certain fonts, but works for other fonts with otherwise the same command?
Date: Tue, 11 Feb 2020 09:24:34 -0500 [thread overview]
Message-ID: <580978a3-ebcb-429d-266e-4c825c61badb@linuxacademy.com> (raw)
In-Reply-To: <87lfp9nr1b.fsf-97jfqw80gc6171pxa8y+qA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 4121 bytes --]
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
<https://linuxacademy.com>
*#1 Learn-by-Doing Multicloud Training Platform*
*Craig Parker*
Technical Writer
Schedule a Meeting or Call <http://www.fossfolks.com>
125 Bear Creek Parkway. Keller. Texas 76248
LinuxAcademy.com <https://linuxacademy.com>
Learn faster and deeper with REAL Hands-On Labs.
<https://linuxacademy.sigstr.net/uc/5d5b0bc61a99af20f77b0db4>
© 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@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.
[-- Attachment #2: Type: text/html, Size: 8470 bytes --]
next prev parent reply other threads:[~2020-02-11 14:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 14:05 tutiluren via pandoc-discuss
[not found] ` <M-oZQZd--3-2-q7wo9g+UVklWk0Htik3J/w@public.gmane.org>
2020-02-11 14:21 ` Joost Kremers
[not found] ` <87lfp9nr1b.fsf-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2020-02-11 14:24 ` Craig Parker [this message]
2020-02-11 14:44 ` tutiluren via pandoc-discuss
[not found] ` <M-ohGso--3-2-q7wo9g+UVklWk0Htik3J/w@public.gmane.org>
2020-02-11 14:46 ` Craig Parker
2020-02-11 17:46 ` John MacFarlane
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=580978a3-ebcb-429d-266e-4c825c61badb@linuxacademy.com \
--to=craigp-uzrat0apdlvlpizirxu/xa@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).