public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Luveh Keraph <1.41421-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Getting pandoc to convert Github Markdown documents with HTML tags to PDF
Date: Mon, 3 Jul 2023 15:41:40 -0700 (PDT)	[thread overview]
Message-ID: <b1dae07b-11d1-4c98-8fcf-369f2b23a54cn@googlegroups.com> (raw)


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

I have a Github Markdown document that contains HTML tags - mostly to do 
with special characters (e.g. &Hscr;) and stuff to place pictures where I 
want in the page. The thing is, pandoc seems to ignore the HTML tags. Is 
this a limitation intrinsic to pandoc, or is there any way to get pandoc to 
process such tags and produce the right output? 

The pandoc invocation that I am currently using for converting my Github 
Markdown documents to PDF is

 $ pandoc --resource-path=/home/abc/Repos.wiki -t html5 
--pdf-engine=wkhtmltopdf --metadata pagetitle="MyDoc.md" --css github.css 
-o MyDoc.pdf

The default invocation pandoc MyDoc.md -o MyDoc.pdf is not dealing with 
images properly (in that it sometimes rearranges surrounding paragraphs the 
wrong way) and it seems to be unable to deal with expressions like 
_A_<sub>_m_</sub>, in that the <sub> and </sub> directives seem to be 
ignored.

-- 
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/b1dae07b-11d1-4c98-8fcf-369f2b23a54cn%40googlegroups.com.

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

             reply	other threads:[~2023-07-03 22:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-03 22:41 Luveh Keraph [this message]
     [not found] ` <b1dae07b-11d1-4c98-8fcf-369f2b23a54cn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-07-04 21:50   ` John MacFarlane
     [not found]     ` <529BC174-779A-4D98-BCC9-F59AEAAC2B9D-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-07-04 23:07       ` Luveh Keraph
     [not found]         ` <CAFy1yb2op3Aq=P4L7xpNwPBBHtopKMx+urWz+-VQ+5Mh0CM=hQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-07-05 18:41           ` John MacFarlane
     [not found]             ` <F4D52E47-33F8-4A2C-9A56-679BD5240ABD-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-07-05 19:16               ` Luveh Keraph
     [not found]                 ` <CAFy1yb3hBrj7FUSM7wDiFY7hEB+GQ1PJSB4RiUo5YRNJnACZjA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-07-05 19:47                   ` John MacFarlane

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=b1dae07b-11d1-4c98-8fcf-369f2b23a54cn@googlegroups.com \
    --to=1.41421-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).