From: Vladimir Alexiev <vladimir.alexiev@ontotext.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Morgan Willcock <morgan@ice9.digital>, emacs-orgmode@gnu.org
Subject: Re: [BUG] ox-md image captions
Date: Wed, 5 Apr 2023 18:30:43 +0300 [thread overview]
Message-ID: <CAMv+wg7C8Rg1KaqK005VGDkVq6o7aakTSJb=aPmZzSngfMrTZA@mail.gmail.com> (raw)
In-Reply-To: <874jpuk2ov.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 1622 bytes --]
I posted a Pandoc request: https://github.com/jgm/pandoc/issues/8752
On Wed, Apr 5, 2023 at 2:04 PM Ihor Radchenko <yantar92@posteo.net> wrote:
> Morgan Willcock <morgan@ice9.digital> writes:
>
> > If ox-md is trying to do the same thing as Markdown.pl then it doesn't
> > really make sense to compare it to CommonMark.
>
> Most likely, ox-md is following Markdown.pl simply because there was no
> better standard at the time ox-md was written.
>
> I now looked up a comparison between markdown flavours (see the attached)
> and I do not see why we should abandon following the original markdown.
> CommonMark and other markdown flavours usually extend things on top of
> the original implementation. So, following Markdown.pl should be the
> most universal option. We leave more specific exporters for advanced
> markdown flavours to external packages.
>
> > The only point am I trying to make is that both ox-md and Pandoc need to
> > deal in the same unambiguous specification in order to inter-operate.
> >
> > For Pandoc, the matching specification needs to be selected to ensure
> > that the correct one is used, but nothing based on Markdown.pl can be
> > unambiguous in this scenario because Markdown.pl has no unambiguous
> > specification.
>
> Indeed.
> I tried to make this point more clear in the attached patch for Org manual.
>
>
> --
> 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>
>
[-- Attachment #2: Type: text/html, Size: 2303 bytes --]
next prev parent reply other threads:[~2023-04-05 15:31 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
2023-04-05 10:41 ` Morgan Willcock
2023-04-05 11:07 ` Ihor Radchenko
2023-04-05 15:30 ` Vladimir Alexiev [this message]
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='CAMv+wg7C8Rg1KaqK005VGDkVq6o7aakTSJb=aPmZzSngfMrTZA@mail.gmail.com' \
--to=vladimir.alexiev@ontotext.com \
--cc=emacs-orgmode@gnu.org \
--cc=morgan@ice9.digital \
--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).