Actually (if I finally understood correctly) there's an open issue for it on the Pandoc repo: https://github.com/jgm/pandoc/issues/7921
Looks like the idea would be to make it an "extension" of Pandoc's markdown.

On Monday, March 20, 2023 at 5:20:40 PM UTC Pablo Rodríguez wrote:
On 3/16/23 22:28, Julien Dutant wrote:
> Ok I think I understand better: you want to add attributes to inlines,
> as in djot [...] Pandoc's internal representation of documents
> doesn't allow attributes *at all* on arbitrary (inline) elements.

Hi Julien,

I wanted attributes for all elements
(https://yewtu.be/watch?v=hFDcoX7s6rE, previously
https://github.com/jgm/pandoc/issues/1966).

AFAIK, these are available for CommonMark with extensions (and for djot?).

I also knew that internally pandoc cannot deal with this natively.

> Your newbie audience would need to understand that:
>
> [this one](https://www.example.org)  is a link
> [that one](:en) is language markup
>
> I don't think it's difficult to master for authoring. Of course it the
> point is rather to teach about markup, the ambiguity isn't great.
> (Though you could consider that unambiguous, e.g. declare that all
> [...](:..) is markup. There's also the issue that you can't combine this
> language attribute with others.

I really appreciate your help, but it seems that a compromise is
required for lightweight language markup. In that case, I‘m going to
wait to explain this.

Many thanks for your help again,

Pablo

--
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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/bb779d38-8c39-478c-a358-27dc1ec86bf4n%40googlegroups.com.