From: Michael Lipp <mnlipp-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Getting started
Date: Fri, 7 Apr 2023 05:19:19 -0700 (PDT) [thread overview]
Message-ID: <21a55a17-06e9-48cf-8deb-e3a2ae113b63n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1097 bytes --]
(I *did* search the web for two hours...)
It shouldn't be that difficult to get started with pandoc, right? Well it
is. I tried the progit example and TeX says that it cannot find font
Helvetica. I tried another example from the web and TeX says it cannot find
font Palatino. I've installed texlive-full on Fedora (that's 4 GB and
specifically inludes a package "texlive-palatino").
Do I really have to understand all about TeX fonts before using pandoc?
From my google results (barely understandable to the uninitiated), this
looks like a several week's effort. That's about the time I wanted to spend
on the document. Am I too stupid and should simply stick to LibreOffice?
--
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/21a55a17-06e9-48cf-8deb-e3a2ae113b63n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1445 bytes --]
next reply other threads:[~2023-04-07 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 12:19 Michael Lipp [this message]
[not found] ` <21a55a17-06e9-48cf-8deb-e3a2ae113b63n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-04-07 13:08 ` Bastien DUMONT
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=21a55a17-06e9-48cf-8deb-e3a2ae113b63n@googlegroups.com \
--to=mnlipp-re5jqeeqqe8avxtiumwx3w@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).