public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: tutiluren via pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: Pandoc Discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: 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 15:05:30 +0100 (CET)	[thread overview]
Message-ID: <M-oZQZd--3-2@tutanota.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2103 bytes --]

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.

Pandoc version: 2.9.1.1

-- 
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/M-oZQZd--3-2%40tutanota.com.

[-- Attachment #2: Type: text/html, Size: 2843 bytes --]

             reply	other threads:[~2020-02-11 14:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11 14:05 tutiluren via pandoc-discuss [this message]
     [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
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=M-oZQZd--3-2@tutanota.com \
    --to=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).