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 18:17:00 -0500 [thread overview]
Message-ID: <adab7ffa8c74278b8495d23452c1729b@isnotmyreal.name> (raw)
In-Reply-To: <871rg7khvw.fsf@gmail.com>
> On 2020-12-02 16:59, Tim Cross wrote:
>> TRS-80 <lists.trs-80@isnotmyreal.name> writes:
>>
>> 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.
>
> From what I can tell, yes your right. However, it also seems that this
> is an arbitrary decision by sourcehut. There doesn't seem to be
> anything
> in the CommonMark spec which prevents the id attribute. The commonMark
> spec explicitly supports raw HTML including attributes. This also makes
> me think the problem is not with the org mode exporter either.
You know, as much as my last email may have sounded otherwise, I am now
also thinking this way.
Whitelisting the id attribute should (in theory) be the least amount of
work. I have replied back on the thread at Sourcehut asking if there is
some (security or other) reason they are blocking it. Hopefully that
approach bears fruit.
> I note that in the email thread you referenced, the last post suggests
> setting up a custom readme format which would allow you to use HTML.
> Maybe that is the easiest route to take - org -> html with custom
> readme?
Unfortunately, the Org HTML exporter (which is in fact the parent that
the Markdown exporter was derived from) also makes extensive use of the
id attribute and anchor links. So I am afraid those would be sanitized
out exactly the same.
Cheers,
TRS-80
next prev parent reply other threads:[~2020-12-02 23:18 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
2020-12-02 21:59 ` Tim Cross
2020-12-02 23:17 ` TRS-80 [this message]
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=adab7ffa8c74278b8495d23452c1729b@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).