Hello Albert, Thanks for your reply, trying weasyprint, solved the problem of the TOC, it introduced some other formatting differences, as I was adapting everything to wkhtmltopdf, Thanks for your suggestion will try to analyze the problem with wkhtmltopdf tho and open a issue on their repo instead of pandoc then. Regards, George. On Wednesday, March 29, 2023 at 2:17:37 PM UTC+2 Albert Krewinkel wrote: > Hi George, > > George Emad writes: > > > 1) Is this a normal use case when I use different file extension than > > the format after -t ? > > Absolutely. Pandoc supports multiple PDF engines, and both the `-t` and > `--pdf-engine` parameters are taken into account when deciding which > format and which engine should be used. If the `--pdf-engine` parameter > is given, then pandoc uses that engine together with the appropriate > output format; if `-t`/`--to` is given then a engine is picket. > > Here's the list of formats and suitable engines: > > - latex: pdflatex, lualatex, xelatex, latexmk, tectonic > - html: wkhtmltopdf, weasyprint, pagedjs, prince > - context: context > - ms: pdfroff > - typst: typst > > The first engine for each format is the default engine. So by using `-t` > you triggered PDF generation through wkhtmltopdf, which, it appears, is > installed on your system. > > > 2) How can I fix this bug with the TOC ? > > My recommendation would be to try one of the alternative engines. If > that doesn't work, please file a bug report in the issue tracker at > https://github.com/jgm/pandoc/issues > > > -- > Albert Krewinkel > GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124 > -- 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/c09063fb-6540-4e79-ba8b-904e3eed4486n%40googlegroups.com.