public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: George Emad <engr.georgeemad-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: What happens when the -t option is different from the file extension after -o
Date: Thu, 30 Mar 2023 01:23:25 -0700 (PDT)	[thread overview]
Message-ID: <c09063fb-6540-4e79-ba8b-904e3eed4486n@googlegroups.com> (raw)
In-Reply-To: <87tty3yco7.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 2148 bytes --]

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 <engr.ge...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 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.

[-- Attachment #1.2: Type: text/html, Size: 3054 bytes --]

  parent reply	other threads:[~2023-03-30  8:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29 11:39 George Emad
     [not found] ` <51f74822-bf97-46c2-864d-1ba0183086e6n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-03-29 11:55   ` Albert Krewinkel
     [not found]     ` <87tty3yco7.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2023-03-29 13:28       ` 'William Lupton' via pandoc-discuss
     [not found]         ` <CAEe_xxg8XZST4fSrEM6j-E=N1o7gzspsQ=VC5G_RCdZXA3NjBA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-03-30  8:23           ` George Emad
     [not found]             ` <861a1c66-4b78-40ae-9e89-8856ac1a6847n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-03-30  8:34               ` 'William Lupton' via pandoc-discuss
2023-03-30  8:23       ` George Emad [this message]
     [not found]         ` <c09063fb-6540-4e79-ba8b-904e3eed4486n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-03-30  9:18           ` Albert Krewinkel
     [not found]             ` <87pm8qy4nx.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2023-03-30 12:54               ` George Emad

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=c09063fb-6540-4e79-ba8b-904e3eed4486n@googlegroups.com \
    --to=engr.georgeemad-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).