From: Ihor Radchenko <yantar92@posteo.net>
To: Morgan Willcock <morgan@ice9.digital>
Cc: Vladimir Alexiev <vladimir.alexiev@ontotext.com>, emacs-orgmode@gnu.org
Subject: Re: [BUG] ox-md image captions
Date: Wed, 05 Apr 2023 10:04:52 +0000 [thread overview]
Message-ID: <877cuqk5kr.fsf@localhost> (raw)
In-Reply-To: <875yaa1x67.fsf@ice9.digital>
Morgan Willcock <morgan@ice9.digital> writes:
>> https://daringfireball.net/projects/markdown/syntax#img
>>
>> Therefore, Org mode is doing everything right within the scope of MD
>> specification we follow. Pandoc does not.
>
> I don't think that Markdown has a single specification.
Indeed. And the one in daringfireball is what we historically follow
since >10 years ago, when ox-md has been implemented.
> Perhaps it is a bug that ox-md is not following a specification, and
> this would be fixed by using a specification and passing its test suite:
Please provide concrete examples where ox-md does not follow
specification.
The title/caption issue herein does not qualify.
https://spec.commonmark.org/0.30/#images also defines
 with "title" being the title, as we currently use
it in ox-md when exporting captions.
> https://commonmark.org/
I agree that using CommonMark.org as the source of truth will make more
sense, given that the original daringfireball.net is not precise.
It would be helpful if someone examines whether ox-md is consistent with
CommonMark.
> However, if ox-md is intentionally trying to match the behaviour of the
> original Markdown.pl, the Pandoc format that matches this is
> "markdown_strict" and not "markdown".
>
> i.e. Pandoc's "markdown" format is not the same format which is
> described at daringfireball.net:
>
> https://pandoc.org/MANUAL.html#pandocs-markdown
Indeed. ox-md is certainly not aiming to export to Pandoc's markdown
flavour.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-04-05 10:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 10:02 [BUG] ox-md image captions Vladimir Alexiev
2023-02-27 18:52 ` Ihor Radchenko
2023-04-04 8:48 ` Ihor Radchenko
2023-04-04 19:34 ` Vladimir Alexiev
2023-04-04 19:41 ` Ihor Radchenko
2023-04-07 14:56 ` Max Nikulin
2023-04-07 15:29 ` Vladimir Alexiev
2023-04-07 17:21 ` Max Nikulin
2023-04-08 10:29 ` Ihor Radchenko
2023-04-08 10:25 ` Ihor Radchenko
2023-04-05 9:43 ` Morgan Willcock
2023-04-05 10:04 ` Ihor Radchenko [this message]
2023-04-05 10:41 ` Morgan Willcock
2023-04-05 11:07 ` Ihor Radchenko
2023-04-05 15:30 ` Vladimir Alexiev
2023-04-16 15:36 ` Ihor Radchenko
2023-04-05 12:06 ` Max Nikulin
2023-04-05 13:05 ` Ihor Radchenko
2023-04-05 15:15 ` Max Nikulin
2023-04-05 15:22 ` Ihor Radchenko
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=877cuqk5kr.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=morgan@ice9.digital \
--cc=vladimir.alexiev@ontotext.com \
/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).