public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Louis <lrannou-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Reference to figures
Date: Fri, 24 Jun 2022 04:31:12 -0700 (PDT)	[thread overview]
Message-ID: <b080bbbc-2ed5-4a1d-a8af-edfd50e7a679n@googlegroups.com> (raw)
In-Reply-To: <874k0a1j19.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>


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

Hello,

I actually know implicit_header_references but I actually misunderstood it. 
I thought this extension was managing the implicit identifier that exists 
in headers.

Then indeed, I think that would be fair to have something similar, maybe 
implicit_caption_references. But maybe that would also be possible to 
extend the implicit_header_references to any identifier ?

Louis

Le vendredi 24 juin 2022 à 11:56:58 UTC+2, Albert Krewinkel a écrit :

> Louis <lra...-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
>

-- 
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/b080bbbc-2ed5-4a1d-a8af-edfd50e7a679n%40googlegroups.com.

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

      parent reply	other threads:[~2022-06-24 11:31 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
     [not found]           ` <874k0a1j19.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-06-24 11:31             ` Louis [this message]

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=b080bbbc-2ed5-4a1d-a8af-edfd50e7a679n@googlegroups.com \
    --to=lrannou-rdvid1duhrbwk0htik3j/w@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).