From: Nicolas Goaziou via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Antero Mejr <mail@antr.me>
Cc: Ricardo Wurmus <rekado@elephly.net>,
andreas@enge.fr, 71849@debbugs.gnu.org
Subject: bug#71849: pdflatex.fmt error using pandoc/pdflatex
Date: Sun, 30 Jun 2024 17:30:11 +0200 [thread overview]
Message-ID: <87o77i8n3w.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87wmm6lba2.fsf@antr.me> (Antero Mejr's message of "Sun, 30 Jun 2024 15:07:17 +0000")
Hello,
Antero Mejr <mail@antr.me> writes:
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> Antero Mejr <mail@antr.me> writes:
>>
>>> When using pandoc to export markdown to PDF, the following error
>>> occurs: [...]
>>
>> Could you please show us what command you used? It's hard to work on
>> this when we can't easily reproduce the problem.
>
> The command was:
> ```
> pandoc -f markdown -t pdf -o out.pdf in.md
> ```
>
> Any markdown file should reproduce the issue.
FWIW, I can export the following "in.md" Markdown file:
--8<---------------cut here---------------start------------->8---
# Titre de niveau 1
## Titre de niveau 2
### Titre de niveau 3
**Texte en gras**
*Texte en italique*
~~Texte barré~~
> Texte cité
- Liste à puces
- Avec plusieurs éléments
1. Liste numérotée
2. Avec plusieurs éléments
`Code en ligne`
--8<---------------cut here---------------end--------------->8---
using the command:
guix shell --pure pandoc texlive-collection-latexrecommended texlive-ulem -- pandoc -f markdown -t pdf -o out.pdf in.md
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2024-06-30 15:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-30 3:54 bug#71849: pdflatex.fmt error using pandoc/pdflatex Antero Mejr
2024-06-30 7:00 ` Ricardo Wurmus
2024-06-30 15:07 ` Antero Mejr
2024-06-30 15:30 ` Nicolas Goaziou via Bug reports for GNU Guix [this message]
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=87o77i8n3w.fsf@nicolasgoaziou.fr \
--to=bug-guix@gnu.org \
--cc=71849@debbugs.gnu.org \
--cc=andreas@enge.fr \
--cc=mail@antr.me \
--cc=mail@nicolasgoaziou.fr \
--cc=rekado@elephly.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.