From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Reference to figures
Date: Fri, 24 Jun 2022 11:48:41 +0200 [thread overview]
Message-ID: <874k0a1j19.fsf@zeitkraut.de> (raw)
In-Reply-To: <ecffcdcd-1788-4565-881b-db436f030e8an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Louis <lrannou-rdvid1DuHRBWk0Htik3J/w@public.gmane.org> writes:
> I don't want an hyperlink but an internal link (<url>#mypic in html).
>
> What I can eventually do is [my picture](#mypic)
>
> ...while for other labels like headers, it only requires [mypic]
Pandoc has a Markdown extension named `implicit_header_references` that
allows [mypic] instead of the longer syntax:
https://pandoc.org/MANUAL#extension-implicit_header_references
So if I understand correctly, you are asking for something like an
`implicit_image_references` extension that would allow to reference a
picture like `![my image caption](mypic.png)` with just `[my image
caption]`.
Did I get that right?
--
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
next prev parent reply other threads:[~2022-06-24 9:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 8:27 Louis
[not found] ` <29a20ffb-c447-4645-8993-3e64938ae105n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-24 8:33 ` Bastien DUMONT
2022-06-24 8:41 ` Louis
[not found] ` <ecffcdcd-1788-4565-881b-db436f030e8an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-24 8:50 ` Bastien DUMONT
2022-06-24 9:00 ` Louis
[not found] ` <f8ad317a-57d3-490e-b42a-d74769d242f4n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-24 9:10 ` Bastien DUMONT
2022-06-24 9:26 ` Louis
[not found] ` <6c9c15fa-d57e-4348-bbf0-44f6a68a2e40n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-24 9:58 ` Bastien DUMONT
2022-06-24 9:48 ` Albert Krewinkel [this message]
[not found] ` <874k0a1j19.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-06-24 11:31 ` Louis
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=874k0a1j19.fsf@zeitkraut.de \
--to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@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).