From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: enlargeable/clickable images
Date: Tue, 25 Oct 2022 10:56:29 -0700 [thread overview]
Message-ID: <768C4D9D-FBFC-41C1-AB1D-C16859CDACBD@gmail.com> (raw)
In-Reply-To: <5a016172-91df-4b07-96c2-ffa0e4081402n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
These are links, not embedded resources. --self-contained is for embedding resources. I don't consider it a bug.
If your document links to an external website, should we be including it, too, in a self-contained HTML page? How would we even do that, since a page is a page, not multiple pages?
> On Oct 24, 2022, at 10:34 PM, Bernhard Donaubauer <bdonauba-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> The longer I think about it the more I consider it a bug. Keeping links to local picture files is in contradiction to *self-contained*.
>
> I will file a bug report.
>
> Regards,
> Bernhard Donaubauer
>
> fiddlosopher schrieb am Montag, 24. Oktober 2022 um 19:28:11 UTC+2:
> That's interesting, I hadn't thought about links to external images with --self-contained.
> I'm not thinking of a good solution, but maybe someone else will have ideas?
>
> > On Oct 24, 2022, at 5:56 AM, Bernhard Donaubauer <bdon...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> >
> > Hello,
> >
> > I'm about to write some documentation with markdown and pandoc.
> >
> > I often use this construct to insert a picture:
> >
> > [![](bilder/600/small.jpg)](bilder/large.jpg)
> >
> > This displays the small picture in the HTML document and loads the large picture if one clicks on the small one.
> >
> > This works so far but is unfortunately incompatible with the self-contained feature.
> >
> > The small picture gets base64 embedded but the large picture stays a link to the local file.
> >
> > Is there a way to embed the large picture too or exists a completely different solution to get this done?
> >
> > Regards
> > Bernhard
> >
> > --
> > 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/d57d8fc0-f4da-44c8-a4e6-bac4dbd249dbn%40googlegroups.com.
>
>
> --
> 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/5a016172-91df-4b07-96c2-ffa0e4081402n%40googlegroups.com.
next prev parent reply other threads:[~2022-10-25 17:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 12:56 Bernhard Donaubauer
[not found] ` <d57d8fc0-f4da-44c8-a4e6-bac4dbd249dbn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-10-24 17:28 ` John MacFarlane
[not found] ` <483ED290-642E-47B9-894C-D9D5F8B1F4F7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-10-25 5:34 ` Bernhard Donaubauer
[not found] ` <5a016172-91df-4b07-96c2-ffa0e4081402n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-10-25 17:56 ` John MacFarlane [this message]
[not found] ` <768C4D9D-FBFC-41C1-AB1D-C16859CDACBD-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-10-26 6:31 ` Bernhard Donaubauer
[not found] ` <bda51ec7-0ccb-40a7-83d0-58242476a483n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-10-26 13:28 ` BPJ
2022-10-26 17:44 ` John MacFarlane
[not found] ` <AEB19120-BB5E-4962-8F80-DA35F240FFD8-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-10-26 19:07 ` Daniel Staal
[not found] ` <78dff09c-fadc-2c8a-8e42-d11246bd2a6b-Jdbf3xiKgS8@public.gmane.org>
2022-10-27 0:27 ` John MacFarlane
2022-10-27 6:38 ` Bernhard Donaubauer
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=768C4D9D-FBFC-41C1-AB1D-C16859CDACBD@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).