From: Randy Yates <yates-EkmVulN54Sk@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Markdown to PDF via TeX: Tyring to change section title color
Date: Sat, 15 May 2021 11:50:53 -0700 (PDT) [thread overview]
Message-ID: <f025f0e7-98ff-4f50-9ba2-37687041fb3dn@googlegroups.com> (raw)
In-Reply-To: <c487e498-4249-4800-ab99-0e3dc9fca664n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2751 bytes --]
Hi Russ,
I hope you don't resent these thoughts since they do not solve your problem
directly, but may I ask why you are trying to go from markdown to latex to
pdf?
Latex is compilable directly to pdf and almost certainly will generate
better pdf than pandoc.
Don't use markdown as your source document format. Latex's capabilities for
generating rich output are far, far greater than markdown, which can't even
generate numbered section headers. Latex also offers:
1. Elegant mathematics
2. An extensive bibliography/citation system
3. The ability to natively generate graphics using Tikz/Pgm.
I've also found an excellent, free tool for converting latex docs to html:
LaTeXML <https://dlmf.nist.gov/LaTeXML/>. It automagically handles
citations. It is even capable of translating many tikz illustrations to
html, e.g. several of the examples here
<https://texample.net/tikz/examples/>.
So in general, choose a source document format that's the least "lossy" in
terms of typographical capability, then translation to other formats incurs
the least loss possible.
--Randy
On Friday, May 14, 2021 at 5:22:02 PM UTC-4 rurq...-Zl5T1cyB3pc@public.gmane.org wrote:
> Hi all,
>
> I found several items on the web about customizing my pdf output from
> Pandoc.
>
> I am calling pandoc with the following parameters:
>
> pandoc *.md -H seccolor.tex -o test_doc.pdf --table-of-contents
> --number-sections --indented-code-classes=javascript
> --highlight-style=monochrome -V mainfont="Palatino" -V documentclass=report
> -V papersize=A5 -V geometry:margin=1in -V monofont="Courier"
> --pdf-engine=xelatex
>
> The seccolor.tex file is:
>
> \usepackage{titlesec}
> \definecolor{DPurple}{rgb}{.75,.52,.153}
> \titleformat*{\section}{\color{DPurple}}
> % \sectionfont{\color{DPurple}}
>
> When i run the command i get:
>
> Error producing PDF.
> ! LaTeX Error: File `titlesec.sty' not found.
>
> Type X to quit or <RETURN> to proceed,
> or enter new name. (Default extension: sty)
>
> Enter file name:
> ! Emergency stop.
> <read *>
>
> l.98 \definecolor
>
> Should i be using another style? I WAS able to generate a standard PDF,
> but just wanted to add a splash of color. From what I read, this snippet of
> TeX should work.
>
> Can anyone suggest how I can fix this?
>
> Thanks,
>
> Russ
>
--
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/f025f0e7-98ff-4f50-9ba2-37687041fb3dn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 3684 bytes --]
next prev parent reply other threads:[~2021-05-15 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AQHXSQcwDnbVHcAVt0CyTplqbe+TqKrkBQMAgAAhy3A=>
2021-05-14 21:22 ` rurq...-Zl5T1cyB3pc@public.gmane.org
[not found] ` <c487e498-4249-4800-ab99-0e3dc9fca664n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-15 7:31 ` gnpan
[not found] ` <8d49ee0f-a978-4cac-9df0-6f0fcb2b6369n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-15 7:34 ` AW: " denis.maier-FfwAq0itz3ofv37vnLkPlQ
[not found] ` <d32560495cc7456bbb78e302aaff271f-FfwAq0itz3ofv37vnLkPlQ@public.gmane.org>
2021-05-15 16:06 ` 'russurquhart1' via pandoc-discuss
[not found] ` <37ef69ff-8fd6-4092-9291-bd7a2515b679n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-15 16:38 ` gnpan
2021-05-15 18:50 ` Randy Yates [this message]
[not found] ` <f025f0e7-98ff-4f50-9ba2-37687041fb3dn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-16 0:12 ` John MacFarlane
[not found] ` <m2eee7mt98.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-05-16 2:14 ` Randy Yates
[not found] ` <47556979-9357-c3d3-b3ed-a3031a195127-EkmVulN54Sk@public.gmane.org>
2021-05-17 12:39 ` Russ Urquhart
2021-05-17 21:13 ` Daniel Staal
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=f025f0e7-98ff-4f50-9ba2-37687041fb3dn@googlegroups.com \
--to=yates-ekmvuln54sk@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).