From: George Emad <engr.georgeemad-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: What happens when the -t option is different from the file extension after -o
Date: Wed, 29 Mar 2023 04:39:10 -0700 (PDT) [thread overview]
Message-ID: <51f74822-bf97-46c2-864d-1ba0183086e6n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1293 bytes --]
Hello,
I am converting some markdown files to a pdf, but I am using a lot of CSS
for formatting,
I found out that if I am using:
*--toc --from=gfm -t html5 -o myfile.pdf*
It actually do keep the css formatting and doesn't convert it to latex
(similar results to opening it in chrome and printing it, with very minor
changes) with one additional bug, with the "TOC table of content"
Description:
It generate a html table of content inside the pdf, so it's broken when you
try to click it,
as it refers to html section <mypag.html#theSection>
I have two questions:
1) Is this a normal use case when I use different file extension than the
format after -t ?
2) How can I fix this bug with the TOC ?
I am pretty new to pandoc, and tried to find the answer in the
documentations and on the mailing list archive, will really appreciate your
help.
Regards,
George
--
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/51f74822-bf97-46c2-864d-1ba0183086e6n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1713 bytes --]
next reply other threads:[~2023-03-29 11:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 11:39 George Emad [this message]
[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
[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=51f74822-bf97-46c2-864d-1ba0183086e6n@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).