From: playduck <robin.prillwitz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Jupyter Notebook to Latex Code Output Image scaling
Date: Thu, 5 Jan 2023 06:43:34 -0800 (PST) [thread overview]
Message-ID: <f00976c4-8dc9-465b-8856-a608b1d52b43n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1364 bytes --]
Hello,
I want to convert a Jupyter Notebook to Latex.
The notebook contains code which outputs images (through matplotlib in my
case).
How do I scale these output images like I can regular markdown images?
Example:
A normal image in Jupyter is defined as:
![](Example.jpg "Test Image"){ width=50% }
and compiled with
pandoc -f ipynb+link_attributes --extract-media=./ -o ./notebook.tex
./notebook.ipynb
which results in the expected latex code:
\includegraphics[width=0.5\textwidth,height=\textheight]{./Example.jpg}
This works as expected.
I want to apply the same scaling to the output of a (python) code block:
import matplotlib.pyplot as plt
plt.plot([1,2,3,4])
plt.show()
The notebook shows the image perfectly fine.
Pandoc nicely exports this as:
\includegraphics{./57d29df1312aa5fb761c415a60dea77444b9136b.png}
How could I define the width here?
The entire notebook.ipynb can be found here:
https://pastebin.com/3k18hJHU
Thanks,
robin
--
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/f00976c4-8dc9-465b-8856-a608b1d52b43n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2362 bytes --]
next reply other threads:[~2023-01-05 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 14:43 playduck [this message]
[not found] ` <f00976c4-8dc9-465b-8856-a608b1d52b43n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-01-05 14:48 ` playduck
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=f00976c4-8dc9-465b-8856-a608b1d52b43n@googlegroups.com \
--to=robin.prillwitz-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).