public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Pedro Bacellar <pbsbacellar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: How to convert from base64 to regular images on the same format (ipynb)?
Date: Wed, 15 Dec 2021 13:11:42 -0800 (PST)	[thread overview]
Message-ID: <16ee16fc-f801-4fc6-b646-5ecec0b044d2n@googlegroups.com> (raw)


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

Hi,

I have a Jupyter notebook with base64 images  and I would like to make a 
copy in which the new notebook does not have base64 images but instead uses 
regular markdown references to images on the filesystem.

I would expect that the command below to do the job, but the new notebook 
still has base64 images.
pandoc test.ipynb --extract-media=images -o output_test.ipynb

I am puzzled, because this works with self contained htmls: if I create a 
self contained html (with base64 images) from the test.ipynb with
pandoc test.ipynb --self-contained --metadata title="test" -o test.html

And then extract the images from this html and output a new html without 
base64 images, everything works as expected.
pandoc test.html --extract-media=images -o output_test.html

What am I missing?

Thanks in advance,
Pedro


-- 
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/16ee16fc-f801-4fc6-b646-5ecec0b044d2n%40googlegroups.com.

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

[-- Attachment #2: test.ipynb --]
[-- Type: application/x-ipynb+json, Size: 10626 bytes --]

                 reply	other threads:[~2021-12-15 21:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=16ee16fc-f801-4fc6-b646-5ecec0b044d2n@googlegroups.com \
    --to=pbsbacellar-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).