From: Morgan Willcock <morgan@ice9.digital>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Vladimir Alexiev <vladimir.alexiev@ontotext.com>,
emacs-orgmode@gnu.org
Subject: Re: [BUG] ox-md image captions
Date: Wed, 05 Apr 2023 10:43:44 +0100 [thread overview]
Message-ID: <875yaa1x67.fsf@ice9.digital> (raw)
In-Reply-To: <87a5zoav86.fsf@localhost> (Ihor Radchenko's message of "Tue, 04 Apr 2023 08:48:41 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
> Upon further investigation, I have found that our base MD reference we
> follow in ox-md is defining image syntax as the following:
>
> ![Alt text](/path/to/img.jpg)
>
> ![Alt text](/path/to/img.jpg "Optional title")
>
> 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.
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:
https://commonmark.org/
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
--
Morgan Willcock
next prev parent reply other threads:[~2023-04-05 9:44 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 [this message]
2023-04-05 10:04 ` Ihor Radchenko
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=875yaa1x67.fsf@ice9.digital \
--to=morgan@ice9.digital \
--cc=emacs-orgmode@gnu.org \
--cc=vladimir.alexiev@ontotext.com \
--cc=yantar92@posteo.net \
/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).