From: TRS-80 <lists.trs-80@isnotmyreal.name>
To: emacs-orgmode@gnu.org
Subject: Re: Exporting .org to .md for Sourcehut (sr.ht); ox-md not following Markdown spec?
Date: Wed, 02 Dec 2020 15:44:50 -0500 [thread overview]
Message-ID: <2eb882bc4d0035d9ca861bfea49b8221@isnotmyreal.name> (raw)
In-Reply-To: <874kl4j8lx.fsf@gmail.com>
> On 2020-12-02 14:44, Tim Cross wrote:
>
> I could be completely wrong here, but I suspect this is a combination
> of the evolving markdown spec (or more specifically, no one standard
> spec) and the age of the org mode markdown exporter.
FWIW, it sort of feels that way to me, too.
> One of the challenges with markdown is that there has never been one
> universally accepted spec.
Yes, I am aware of the history. And this is one of my main criticisms
of Markdown, and why I prefer Orgmode (by a wide margin). In fact I
agree (strongly) with Karl Voit's article "Org-Mode Is One of the Most
Reasonable Markup Languages to Use for Text."[0]
> It might be worth looking in the archive. I seem to recall other
> discussions along these lines some months back. My flawed memory seems
> to recall that it was probably time for org's markdown exporter to be
> updated to fit with the more 'common' markdown standard, but I don't
> recall which that was or whether anyone decided to take that
> responsibility on.
Thanks, I'll have a look. I was also sort of getting the sense that
updating the Markdown exporter might be the answer, hence me starting
this thread.
> Org already has two markdown flavors - 'generic' markdown and github
> flavoured markdown. Org's current markdown is based on
> http://daringfireball.net/projects/markdown, which probably varies
> enough from the one used by sourcehut to cause the problems you are
> seeing.
I think the problem is actually because Sourcehut are sanitizing the id
attribute out of links, as I have replied already to some other people
in this thread.
> Unfortunately, this fails to provide a clear path to fix your problem.
Yeah, this is like (at least) my second day into this now. :) Which is
why I paused to seek more counsel on the best way forward. As there
seem to be no good/clear (or at least, easy) answers.
Thanks for the input.
Cheers,
TRS-80
[0] https://karl-voit.at/2017/09/23/orgmode-as-markup-only/
next prev parent reply other threads:[~2020-12-02 20:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 18:52 Exporting .org to .md for Sourcehut (sr.ht); ox-md not following Markdown spec? TRS-80
2020-12-02 19:12 ` Jean Louis
2020-12-02 19:56 ` TRS-80
2020-12-02 21:32 ` TRS-80
2020-12-02 19:44 ` Tim Cross
2020-12-02 20:44 ` TRS-80 [this message]
2020-12-02 21:59 ` Tim Cross
2020-12-02 23:17 ` TRS-80
2020-12-02 23:36 ` Tim Cross
2020-12-02 19:45 ` Diego Zamboni
2020-12-02 20:25 ` TRS-80
2020-12-11 15:53 ` TRS-80
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2eb882bc4d0035d9ca861bfea49b8221@isnotmyreal.name \
--to=lists.trs-80@isnotmyreal.name \
--cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).