From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Exporting .org to .md for Sourcehut (sr.ht); ox-md not following Markdown spec?
Date: Thu, 03 Dec 2020 10:36:01 +1100 [thread overview]
Message-ID: <87wnxzixwe.fsf@gmail.com> (raw)
In-Reply-To: <adab7ffa8c74278b8495d23452c1729b@isnotmyreal.name>
TRS-80 <lists.trs-80@isnotmyreal.name> writes:
>> On 2020-12-02 16:59, Tim Cross wrote:
>>> TRS-80 <lists.trs-80@isnotmyreal.name> writes:
>>>
>> 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.
>
OK. My reading of that response was that the custom approach would give
you full control over the HTML. If they still run some sort of
sanitiser, then you would still have an issue as you actually don't have
full control. However, that does seem like an odd process. I mean, if
you go to the trouble to setup a custom workflow and then having some
arbitrary sanitiser come in at the end and move the goal posts seems
broken to me.
--
Tim Cross
next prev parent reply other threads:[~2020-12-02 23:36 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
2020-12-02 23:36 ` Tim Cross [this message]
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=87wnxzixwe.fsf@gmail.com \
--to=theophilusx@gmail.com \
--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).