From: Steven Jan <stevenbjan1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: LaTeX + Standalone
Date: Tue, 1 Nov 2022 08:56:09 -0700 (PDT) [thread overview]
Message-ID: <fe0033a7-6a89-4535-b0b4-a2db9bb62c72n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1006 bytes --]
Hello,
I am using Pandoc to convert a very complex book from LaTeX to EPUB3. The
book's chapters are linked to by means of \include{} directives. Certain
figures in the chapters are TikZ drawings (created using Mathc
<https://www.mathcha.io/editor>ha <https://www.mathcha.io/editor>), pulled
into the chapter from separate .tex files using \includestandalone. While
.png graphics are showing correctly in the EPUB3, standalones are not. Does
anybody know how to get standalones to compile before Pandoc converts to
EPUB3 (if that is the correct sequence)? Thank you.
Best wishes,
Steven.
--
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/fe0033a7-6a89-4535-b0b4-a2db9bb62c72n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1343 bytes --]
next reply other threads:[~2022-11-01 15:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 15:56 Steven Jan [this message]
[not found] ` <fe0033a7-6a89-4535-b0b4-a2db9bb62c72n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-01 16:15 ` Bastien DUMONT
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=fe0033a7-6a89-4535-b0b4-a2db9bb62c72n@googlegroups.com \
--to=stevenbjan1-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).