public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: enlargeable/clickable images
Date: Wed, 26 Oct 2022 17:27:42 -0700	[thread overview]
Message-ID: <4567DD82-FE64-41F2-BB56-DDDD32AAD5A7@gmail.com> (raw)
In-Reply-To: <78dff09c-fadc-2c8a-8e42-d11246bd2a6b-Jdbf3xiKgS8@public.gmane.org>



> On Oct 26, 2022, at 12:07 PM, Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org> wrote:
> 
> On 10/26/22 1:44 PM, John MacFarlane wrote:
>>> On Oct 25, 2022, at 11:31 PM, Bernhard Donaubauer <bdonauba-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>>> 
>>> 
>>>> These are links, not embedded resources. --self-contained is for embedding resources. I don't consider it a bug.
>>> 
>>> Yes these are links but links to local resources. Image files that are in the same directory as my MD file.
>>> As far as I know the current browser generation has support for DATA URI in the href attribute, so it's
>>> technically feasible.
>> Do you mean
>> <a href="data:...">link text</a>
>> This didn't work when I tried it.
>> In any case, I don't think what you're asking for is consistent with the documented and intended behavior of --self-contained.
>> Note that --self-contained embeds BOTH internal and external images. Why should it behave differently if it were extended to links?
> 
> Because a link isn't garunteeded to be an image - or even a single file.  It could be dynamically generated, an index, a 3-hour video, or pretty much anything.  (And owned by pretty much anyone.)  All we know is that it's an external resource that we're linking to.

Just to be clear: I’m not arguing that —self-contained should embed the contents of external links.  I’m saying it would be inconsistent to make it embed the contents of internal links, but not external ones, because it doesn’t make that distinction for images.  I’m not in favor of any link embedding (nor do I understand how we’d achieve it technically).

-- 
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/4567DD82-FE64-41F2-BB56-DDDD32AAD5A7%40gmail.com.


  parent reply	other threads:[~2022-10-27  0:27 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
     [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 [this message]
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=4567DD82-FE64-41F2-BB56-DDDD32AAD5A7@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).