public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: A A <amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Including SVGs with LaTeX math in Pandoc?
Date: Mon, 6 Mar 2023 16:11:37 +0100	[thread overview]
Message-ID: <CAMwawgPKcXu-CapB6d_vSWc7=vfA_sQSzFnnv4nGBurq6+MkEw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1529 bytes --]

I’d like to include SVG graphics in my LaTeX document using pandoc. I
understand this is currently not supported
<https://github.com/jgm/pandoc/issues/265> so I have resorted to the idea
of performing the SVG to PDF conversion externally and then including in my
markdown using something like this:

![whee](foo.pdf)

I would prefer not to do this conversion using raw inkscape because the svg
package in LaTeX has the added advantage of rendering LaTeX math within the
figure if it encounters LaTeX math in the SVG. This won’t happen if I only
use inkscape.

Unfortunately, I haven’t found a way to ensure that the resulting PDF is
cropped to the extents of the image *after* doing a LaTeX compilation. For
example:

\documentclass{article}

\usepackage{svg}

\begin{document}
    \includesvg[scale=1.0]{idea.svg}

\end{document}

will compile as a full A4 sized page with page number. If I then include it
in my markdown as ![idea](idea.pdf) I’d get the whole page as my “figure”
and not only the SVG.

How can include SVGs with LaTeX math in Pandoc ?

-- 
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/CAMwawgPKcXu-CapB6d_vSWc7%3DvfA_sQSzFnnv4nGBurq6%2BMkEw%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 5756 bytes --]

             reply	other threads:[~2023-03-06 15:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06 15:11 A A [this message]
2023-03-06 15:46 Bastien DUMONT
2023-03-06 15:53 ` A A
     [not found]   ` <CAMwawgNE1b+Lzo6edzZsOX_PA-Z9TDPVFKecb-CEFuy2cK0LXw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-03-13  0:59     ` Julien Dutant

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='CAMwawgPKcXu-CapB6d_vSWc7=vfA_sQSzFnnv4nGBurq6+MkEw@mail.gmail.com' \
    --to=amine.aboufirass-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).