From: Craig Parker <craigp-UzRat0APdLvLPIzirxu/xA@public.gmane.org>
To: tutiluren via 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 09:46:50 -0500 [thread overview]
Message-ID: <e6ceb7c0-b82f-cc32-e25e-e0fc5d961104@linuxacademy.com> (raw)
In-Reply-To: <M-ohGso--3-2-q7wo9g+UVklWk0Htik3J/w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 3040 bytes --]
The list has already seen this, so I'm just sending it to you...
Give HTML to PDF another whirl. It's fine with WeasyPrint. I've got a
walkthrough (and a template you can grab on github) here:
https://linuxacademy.com/blog/tutorials/convert-markdown-to-pdf-tutorial/
On 2/11/20 9:44 AM, tutiluren via pandoc-discuss wrote:
>
> 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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> <mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@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
> <https://groups.google.com/d/msgid/pandoc-discuss/M-ohGso--3-2%40tutanota.com?utm_medium=email&utm_source=footer>.
--
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/e6ceb7c0-b82f-cc32-e25e-e0fc5d961104%40linuxacademy.com.
[-- Attachment #2: Type: text/html, Size: 7291 bytes --]
next prev parent reply other threads:[~2020-02-11 14:46 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
[not found] ` <M-ohGso--3-2-q7wo9g+UVklWk0Htik3J/w@public.gmane.org>
2020-02-11 14:46 ` Craig Parker [this message]
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=e6ceb7c0-b82f-cc32-e25e-e0fc5d961104@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).