From: BPJ <bpj-J3H7GcXPSITLoDKTGw+V6w@public.gmane.org>
To: pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>,
bdonauba-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: enlargeable/clickable images
Date: Wed, 26 Oct 2022 15:28:01 +0200 [thread overview]
Message-ID: <CADAJKhCf8v8aodqv7QONpvy3-fatesMUKehUpgxsCV=PMr19jA@mail.gmail.com> (raw)
In-Reply-To: <bda51ec7-0ccb-40a7-83d0-58242476a483n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2203 bytes --]
If the OP wants to modify the actual HTML files rather than using
JavaScript the attached Perl script might be of interest.
Den ons 26 okt. 2022 08:32Bernhard Donaubauer <bdonauba-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> skrev:
>
> > 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.
>
>
> > 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?
>
> Links to external web sites and resources shouldn't be changed of course.
> But In my opinion one should here differentiate between:
>
> href="images/mypic.png"
>
> and
>
> href="https://www.wikipedia.de"
>
>
> In the meantime I was able to implement this feature with the help of a
> javascript library, so I won't argue but I would have preferred a pure
> markdown solution.
>
> 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-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/bda51ec7-0ccb-40a7-83d0-58242476a483n%40googlegroups.com
> <https://groups.google.com/d/msgid/pandoc-discuss/bda51ec7-0ccb-40a7-83d0-58242476a483n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
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/CADAJKhCf8v8aodqv7QONpvy3-fatesMUKehUpgxsCV%3DPMr19jA%40mail.gmail.com.
[-- Attachment #1.2: Type: text/html, Size: 3222 bytes --]
[-- Attachment #2: html-base64.zip --]
[-- Type: application/zip, Size: 104745 bytes --]
next prev parent reply other threads:[~2022-10-26 13:28 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 [this message]
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='CADAJKhCf8v8aodqv7QONpvy3-fatesMUKehUpgxsCV=PMr19jA@mail.gmail.com' \
--to=bpj-j3h7gcxpsitlodktgw+v6w@public.gmane.org \
--cc=bdonauba-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).