From: BP Jonsson <bpj-J3H7GcXPSITLoDKTGw+V6w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Pandoc crashes when converting from md to pdf directly
Date: Fri, 1 Apr 2016 18:08:36 +0200 [thread overview]
Message-ID: <56FE9D04.2090403@gmail.com> (raw)
In-Reply-To: <ae9a22d5-9f83-43aa-9bf2-d9867ccc811a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Den 2016-04-01 kl. 14:07, skrev G B:
> Oddly enough doing pandoc --toc source.md -o out.tex then pandoc --toc
> out.tex -o out.pdf works...
>
> Please help me by telling you how to provide more info so we can get to the
> source of this.
My guess is that there is something in your metadata which changes
the preamble in some way. The difference is that unlike `pandoc
--toc source.md -o out.pdf` the command `pandoc --toc source.md -o
out.tex` creates a .tex file without a preamble, so that when you
run `pandoc --toc out.tex -o out.pdf` a 'default' preamble without
any modifications will be used.
First of all try to use XeLaTeX instead of pdfLaTeX:
```
pandoc --toc --latex-engine=xelatex source.md -o out.pdf
```
If you have any language or font-setting stuff in your metadata
you may have to change those to use polyglossia/fontspec too.
If that doesn't work try doing this
```
pandoc --toc source.md -o out0.tex
pandoc --toc source.md --standalone -o out1.tex
pandoc --toc out0.tex --standalone -o out2.tex
```
then run diff, or since you seem to be on Windows FC, on out1.tex
and out2.tex. Seeing the differences between the two should give
you a clue what is going on.
http://www.howtogeek.com/206123/how-to-use-fc-file-compare-from-the-windows-command-prompt/
next prev parent reply other threads:[~2016-04-01 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 12:07 G B
[not found] ` <ae9a22d5-9f83-43aa-9bf2-d9867ccc811a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-04-01 16:08 ` BP Jonsson [this message]
[not found] ` <56FE9D04.2090403-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-04 1:28 ` Guilherme
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=56FE9D04.2090403@gmail.com \
--to=bpj-j3h7gcxpsitlodktgw+v6w@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).