From: tutiluren via pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: Pandoc Discuss <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 15:44:10 +0100 (CET) [thread overview]
Message-ID: <M-ohGso--3-2@tutanota.com> (raw)
In-Reply-To: <87lfp9nr1b.fsf-97jfqw80gc6171pxa8y+qA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1306 bytes --]
> 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.)
>
Thanks for clarifying. However, the file name for Courier/Courier Standard on my Windows 10 is actually "coure.fon" (it was tricky to find out, because that particular dir behaves very differently from all others), but the same principle holds: only "modern" font formats seem to work.
There sure are a lot of death traps on the way to converting a PDF document! And this is for a fixed-letter-size, fixed-column-width, plaintext document... After the nightmare I went through a few years ago, I won't ever even *try* to convert a fancy HTML + CSS document to PDF ever again!
--
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-ohGso--3-2%40tutanota.com.
[-- Attachment #2: Type: text/html, Size: 1872 bytes --]
next prev parent reply other threads:[~2020-02-11 14:44 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
2020-02-11 14:44 ` tutiluren via pandoc-discuss [this message]
[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-ohGso--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).