[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Exporting .org to .md for Sourcehut (sr.ht); ox-md not following Mar
From: |
TRS-80 |
Subject: |
Re: Exporting .org to .md for Sourcehut (sr.ht); ox-md not following Markdown spec? |
Date: |
Wed, 02 Dec 2020 14:56:20 -0500 |
User-agent: |
Roundcube Webmail/1.3.15 |
On 2020-12-02 14:12, Jean Louis wrote:
Try using pandoc Org to Markdown as that could help until Org
exporting start working how it should.
Great minds must think alike! :) I tried that already but in-page
links
which look like:
```
[[*Setup][Setup]]
```
Somehow get exported to:
```
*Setup*
```
...which is not a link at all, but rather just italicised text.
In fact, I think I will go now and bring that up to pandoc project...
They have several different flavored Markdown exporters available, I
tried all of them in fact.
FWIW, I also tried going the route of exporting to HTML (which is also
supported at Sourcehut)[0] however I ran into lots of other similar
issues like in OP, as the HTML exporter does the same things with id in
links.
I actually worked on this all day yesterday, still without success. I
am of course still open to any suggestions, but I came to conclusion so
far that fixing the ox-md exporter might be the Right Way and I was
willing to dig into that further, myself.
I work extensively in Orgmode and have plans to publish many more things
(likely on Sourcehut) and I would rather do whatever work is required to
fix ox-md than change all my existing (or new) work to Markdown. I
really do hate Markdown that much. :D
Also, maybe in the meantime I could simply hard code a ToC, but that
still will not fix other in-page links throughout the page (like the
*Setup example, above).
Cheers,
TRS-80
[0] https://man.sr.ht/git.sr.ht/#setting-a-custom-readme