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: Adding attributes to definition lists using pandoc
Date: Fri, 15 Jul 2022 11:28:27 +0200	[thread overview]
Message-ID: <447D8C10-40D3-41EF-AEA2-B18727AD269D@gmail.com> (raw)
In-Reply-To: <CAMwawgMECRkn7n5G3cj+i=imJuUZeciPN82mVQAZZtPc7yJqRA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Indeed, even with commonmark_x the attributes are not getting picked up on the definition list.

Note:  pandoc's AST cannot currently attach attributes directly to a definition list.  So generally the commonmark_x reader will create a containing Div to which to apply the attributes.  You can test that by attaching an attribute to a paragraph.  For some reason, it isn't working with definition lists.  This is a bug in https://github.com/jgm/commonmark-hs and should be reported there.


> On Jul 13, 2022, at 5:17 PM, A A <amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> 
> Looks like it might be a bug.... anyone else?
> 
> On Wed, 13 Jul 2022 at 17:14, Sukil Etxenike arizaleta <sukiletxe@gmail.com> wrote:
> Hi,
> 
> I've tried it too, and it gives the same results. I don't know why this happens.
> 
> Regards,
> 
> Sukil
> 
> 
> 
> El 13/07/2022 a las 17:01, A A escribió:
>> Dear Sukil,
>> 
>> So I believe only  commonmark_x provides the non-default attributes extension. It’s not included in commonmark, I don’t think.
>> 
>> So I tried with commonmark_x on the following code:
>> 
>> ---
>> title: my title
>> author: bob marley
>> ---
>> 
>> # Header {#identifier .class key=value}
>> 
>> Some text
>> 
>> {#special .glossary}
>> Term 1
>> : Definition 1
>> 
>> Term 2
>> : Definition 2
>> 
>> with the following command:
>> 
>> pandoc -f commonmark_x -t html .\definition-lists.md
>> 
>> But i’m still not getting the attributes added to the <dl> element:
>> 
>> <h1 class="class" data-key="value" id="identifier">Header</h1>
>> <p>Some text</p>
>> <dl>
>> <dt>Term 1</dt>
>> <dd>
>> Definition 1
>> </dd>
>> <dt>Term 2</dt>
>> <dd>
>> Definition 2
>> </dd>
>> </dl>
>> 
>> The other option is to maybe use the fenced_divs extension with regular markdown, but I’m trying to see if there’s a more generic way.
>> 
>> Regards,
>> 
>> Amine
>> 
>> 
>> On Wed, 13 Jul 2022 at 16:42, Sukil Etxenike arizaleta <sukiletxe@gmail.com> wrote:
>> Hi,
>> 
>> OK, technically it doesn't say it cannot be done, it only says that this syntax is only available in headers, divs, spans, links and images.
>> 
>> But wait, checking non-default extensions, if you convert from commonmark or commonmark_x you can use this syntax with any element of the AST. Technically it wuld add an enclosing div, too.
>> 
>> This, however, wouldn't let you enable other extensions, check --list-extensions=commonmark etc. to see if this would suit you.
>> 
>> Hth,
>> 
>> Sukil
>> 
>> 
>> 
>> El 13/07/2022 a las 16:32, A A escribió:
>>> Hi Sukil,
>>> 
>>> Thanks for your quick response, but where in the manual does it say that this cannot be done? I was under the impression that using the braced syntax to add attributes was a sort of universal thing that could be done to any of the elements in the AST?
>>> 
>>> Regards,
>>> 
>>> Amine
>>> 
>>> On Wed, 13 Jul 2022 at 16:29, Sukil Etxenike arizaleta <sukiletxe@gmail.com> wrote:
>>> According to the manual: no, but you can enclose it in a div and give that div the attributes you want.
>>> 
>>> Hth,
>>> 
>>> Sukil
>>> 
>>> 
>>> 
>>> El 13/07/2022 a las 16:18, A A escribió:
>>>> Dear All,
>>>> 
>>>> I would like to ask whether it is possible to assign attributes, identifiers or key-value pairs to definition lists as follows in pandoc:
>>>> 
>>>> ---
>>>> title: my title
>>>> author: bob marley
>>>> ---
>>>> 
>>>> # Header {#identifier .class key=value}
>>>> 
>>>> Some text
>>>> 
>>>> {.glossary}
>>>> Term 1
>>>> : Definition 1
>>>> 
>>>> Term 2
>>>> : Definition 2
>>>> 
>>>> Compiling the above with pandoc -f markdown -t html .\definition-lists.md generates the following:
>>>> 
>>>> <h1 class="class" data-key="value" id="identifier">Header</h1>
>>>> <p>Some text</p>
>>>> <p>{.glossary} Term 1 : Definition 1</p>
>>>> <dl>
>>>> <dt>Term 2</dt>
>>>> <dd>
>>>> Definition 2
>>>> </dd>
>>>> </dl>
>>>> 
>>>> The attributes on the header are getting picked up by pandoc, but not on the definition list. What am I doing wrong here?
>>>> 
>>>> Regards,
>>>> 
>>>> Amine
>>>> 
>>>> -- 
>>>> 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/CAMwawgOyf796%3DsXy5Zt%2BT1Z0MZqXyLZS-YJCqRWRCkzyF-Lh_g%40mail.gmail.com.
>>> -- 
>>> 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/6a4255a0-557b-a182-43a8-35facb1e2788%40gmail.com.
>>> -- 
>>> 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/CAMwawgOYU8Z6XZ6uMxZ5t1-47OV7FKR7640O2hSb_VHStu3yAw%40mail.gmail.com.
>> -- 
>> 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/b187e3c4-0026-1853-d18f-86cedce39191%40gmail.com.
>> -- 
>> 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/CAMwawgPPQCVG_xQfVoQD7nPqaU8ObZd%2BcM5gcqEXuuy3ouPBFw%40mail.gmail.com.
> 
> -- 
> 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/fa49db14-b03b-f29d-32bc-daf4b80d6b39%40gmail.com.
> 
> -- 
> 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/CAMwawgMECRkn7n5G3cj%2Bi%3DimJuUZeciPN82mVQAZZtPc7yJqRA%40mail.gmail.com.

-- 
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/447D8C10-40D3-41EF-AEA2-B18727AD269D%40gmail.com.


      parent reply	other threads:[~2022-07-15  9:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13 14:18 A A
     [not found] ` <CAMwawgOyf796=sXy5Zt+T1Z0MZqXyLZS-YJCqRWRCkzyF-Lh_g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-07-13 14:29   ` Sukil Etxenike arizaleta
     [not found]     ` <6a4255a0-557b-a182-43a8-35facb1e2788-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-07-13 14:32       ` A A
     [not found]         ` <CAMwawgOYU8Z6XZ6uMxZ5t1-47OV7FKR7640O2hSb_VHStu3yAw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-07-13 14:42           ` Sukil Etxenike arizaleta
     [not found]             ` <b187e3c4-0026-1853-d18f-86cedce39191-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-07-13 15:01               ` A A
     [not found]                 ` <CAMwawgPPQCVG_xQfVoQD7nPqaU8ObZd+cM5gcqEXuuy3ouPBFw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-07-13 15:14                   ` Sukil Etxenike arizaleta
     [not found]                     ` <fa49db14-b03b-f29d-32bc-daf4b80d6b39-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-07-13 15:17                       ` A A
     [not found]                         ` <CAMwawgMECRkn7n5G3cj+i=imJuUZeciPN82mVQAZZtPc7yJqRA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-07-15  9:28                           ` John MacFarlane [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=447D8C10-40D3-41EF-AEA2-B18727AD269D@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).