Re: Exporting .org to .md for Sourcehut (sr.ht); ox-md not following Markdown spec?

[TRS-80]

> > On Wed, Dec 2, 2020 at 7:54 PM TRS-80 <lists.trs-80@isnotmyreal.name>
> > wrote:
> >
> > Some further digging revealed that the ox-md exporter (which itself
> > is derived from the HTML exporter(?) makes extensive use of the id
> > attribute in links.  And Sourcehut's HTML sanitizer only allows href
> > and title attributes (not id).[1]
> >
> > [1] https://man.sr.ht/markdown/#post-processing

> On 2020-12-02 14:45, Diego Zamboni wrote:
>
> (note: Markdown allows embedded HTML, so ox-md's behavior is not
> incorrect)

Right.  However, unless I am missing something, they (Sourcehut) are
passing the HTML through, but their sanitizer is only allowing a subset
of attributes.  Look closely (on the sr.ht Markdown page we both have
now linked) at what attributes are allowed for links:

a: href, title

Only href and title.  No id!

> Note that according to https://man.sr.ht/markdown/#post-processing,
> Sourcehut uses CommonMark, not plain Markdown, so I guess that's why
> it doesn't allow all HTML tags.

Yes, I am aware they use CommonMark.

However it seems to me that CommonMark is just a less ambiguously
defined version of Markdown, designed to address those particular
criticisms of the original.

I don't know if there is anything in CommonMark spec itself that forbids
passing HTML through, and I did not bother to look that up (and thus I
could be wrong) however I think the problem is rather what I already
said above about id attributes being blocked, by Sourcehut particular
HTML sanitizer.

> There seems to be no ox-commonmark (that I could find) but pandoc does
> support it, so you could probably use ox-pandoc
> (https://github.com/kawabata/ox-pandoc) to export your documents in
> CommonMark format.

I did try using command line pandoc, and ran into some problems (which I
outlined already in separate reply to Jean Louis), but maybe I give this
a try, too.  Thanks.

Cheers,
TRS-80