public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Jupyter-to-LaTex | How to render tables?
Date: Mon, 18 Jul 2022 09:54:11 +0200	[thread overview]
Message-ID: <5299A394-419C-4839-B528-46D002AF3371@gmail.com> (raw)
In-Reply-To: <6c82ec4b-d697-41a6-9192-2a84945e0850n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Raw HTML in a Markdown document (which is apparently what the R display_html function produces) will not be passed through to PDF.  Similarly, raw LaTeX will not be passed through to HTML.

One approach might be to generate *both* formats in your notebook.  You could try that.

Another approach would be to use a Lua filter that matches raw HTML blocks and uses pandoc.read to convert them to native pandoc tables, which could then be rendered in PDF.  I believe there are examples of such filters either in the Lua filters documentation, or in the pandoc/lua-filters repository, or on this list.  If you can't see how to do it, just ask.


-- 
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/5299A394-419C-4839-B528-46D002AF3371%40gmail.com.


  parent reply	other threads:[~2022-07-18  7:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6c82ec4b-d697-41a6-9192-2a84945e0850n@googlegroups.com>
2022-07-17 23:40 ` Richard Huntsinger
     [not found] ` <6c82ec4b-d697-41a6-9192-2a84945e0850n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-18  7:54   ` John MacFarlane [this message]
     [not found]     ` <5299A394-419C-4839-B528-46D002AF3371-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-07-19  1:40       ` Richard Huntsinger
     [not found]         ` <1568e512-a488-495c-a82d-aedec432d0acn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-19 17:17           ` Richard Huntsinger
     [not found]             ` <ebb070e8-7bcc-4584-b142-5a4a150def08n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-21 20:29               ` Richard Huntsinger

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=5299A394-419C-4839-B528-46D002AF3371@gmail.com \
    --to=fiddlosopher-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).