From: "'William Lupton' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Assigning identifiers to definition items
Date: Mon, 6 Nov 2023 15:02:06 +0000 [thread overview]
Message-ID: <CAEe_xxiyw7-04ghifFmDDv3XH0rBVL-WszRX44=27Q_OP+XSnA@mail.gmail.com> (raw)
In-Reply-To: <CAMwawgNTwDo55QU5dZsgeXQpG9jAr1_RevLPdshEjFgqyF=gLQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2445 bytes --]
You can use bracketed spans
<https://pandoc.org/MANUAL.html#extension-bracketed_spans> to do this
manually, as in:
[Term 1]{#term-1}
...
Reference to [Term 1](#term-1).
We use an *auto-identifiers.lua* filter that I could probably add to
pandoc-ext <https://github.com/pandoc-ext>. This will auto-derive the
identifiers from the span content. This allows you to write this:
[Term 1]{}
...
Reference to [Term 1]().
or this (the t: is used as a prefix):
[Term 1]{#t:}
...
Reference to [Term 1](#t:).
The latter example generates this HTML.
<dt><span id="t:term-1">Term 1</span></dt>
...
<p>Reference to <a href="#t:term-1">Term 1</a>.</p>
On Mon, 6 Nov 2023 at 12:14, A A <amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Pandoc will convert the following markdown:
>
> Term 1
>
> : Definition 1
>
> : Definition 2
>
> Term 2
>
> : Definition 1
>
> To the following HTML:
>
> <dl>
> <dt>Term 1</dt>
> <dd>
> <p>Definition 1</p>
> </dd>
> <dd>
> <p>Definition 2</p>
> </dd>
> <dt>Term 2</dt>
> <dd>
> <p>Definition 1</p>
> </dd>
> </dl>
>
> How easy/straightforward is it to assign identifiers to specific
> *definition* items in markdown? For example such that the resulting HTML
> looks like the following:
>
> <dl>
> <dt>Term 1</dt>
> <dd id="def-1-term-1">
> <p>Definition 1</p>
> </dd>
> <dd>
> <p>Definition 2</p>
> </dd>
> <dt>Term 2</dt>
> <dd>
> <p>Definition 1</p>
> </dd>
> </dl>
>
> --
> 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/CAMwawgNTwDo55QU5dZsgeXQpG9jAr1_RevLPdshEjFgqyF%3DgLQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/pandoc-discuss/CAMwawgNTwDo55QU5dZsgeXQpG9jAr1_RevLPdshEjFgqyF%3DgLQ%40mail.gmail.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/CAEe_xxiyw7-04ghifFmDDv3XH0rBVL-WszRX44%3D27Q_OP%2BXSnA%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 6806 bytes --]
next prev parent reply other threads:[~2023-11-06 15:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 12:13 A A
[not found] ` <CAMwawgNTwDo55QU5dZsgeXQpG9jAr1_RevLPdshEjFgqyF=gLQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-11-06 15:02 ` 'William Lupton' via pandoc-discuss [this message]
[not found] ` <CAEe_xxiyw7-04ghifFmDDv3XH0rBVL-WszRX44=27Q_OP+XSnA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-11-11 21:57 ` A A
2023-11-11 22:57 ` Bastien DUMONT
2023-11-12 10:05 ` A A
[not found] ` <CAMwawgNoS75CPOstiM0Xv7xtBLK+Ff3Jp1o2udPnBQaHhH06VQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-11-12 10:13 ` A A
[not found] ` <CAMwawgM3gEOSrSQFvE9k2_6+J=gmvW0MP6bo6dXVBvNNagufTQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-11-12 10:27 ` A A
[not found] ` <CAMwawgMH_vudUviXZa8odQ-jyn5Snk3YYGzx4K9to2RBQ_dpOA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-11-12 10:50 ` 'William Lupton' via pandoc-discuss
[not found] ` <CAEe_xxjOecwEVJSiO+BQDVHqc1zaDxHZuuzDSTDjZEmQna4xOg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-11-12 16:35 ` A A
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='CAEe_xxiyw7-04ghifFmDDv3XH0rBVL-WszRX44=27Q_OP+XSnA@mail.gmail.com' \
--to=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).