public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Beni Cherniavsky-Paskin <beni.cherniavsky-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: History of the math syntax
Date: Fri, 20 May 2022 14:35:13 +0300	[thread overview]
Message-ID: <CALJxei+=6CLro5VK9o-u2JaX46d3n8XcFtiDASOU3gUtMkOD5w@mail.gmail.com> (raw)
In-Reply-To: <87pmk88xxr.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 5175 bytes --]

[I'm only familiar with these projects after they existed, happy to be
corrected if my reconstruction is wrong]

I _suspect_ MultiMarkdown was the first.  It started out as a fork of
Gruber's Markdown.pl, and IIRC the whole point of "multi" in the name was
the novelty (at least in context of markdown) of having multiple output
formats, including LaTeX.
(googling...) See:
https://github.com/fletcher/MultiMarkdown/wiki/MultiMarkdown-Syntax-Guide#math-support
https://github.com/fletcher/MultiMarkdown/wiki/Version-Histor
https://fletcher.github.io/MultiMarkdown-6/introduction.html#whatarethedifferentversionsofmultimarkdown
Surprisingly however, early versions until 3.0 emitted LaTeX (including
math!), by XSLT conversion from HTML including MathML!
(The first git commit I can find
https://github.com/fletcher/MultiMarkdown/commit/f7fcb4af5fdb83f58feaf4b8ec93bf689ca25fc6,
not sure where if pre-git code is available)

From there, math support spread to many other implementations, with
experimentation both in source syntax and output techniques...
(MultiMarkdown itself switched formula input syntax from AsciiMath to TeX,
and changed delimiters.)

Early markdown extensions were pretty much free-for-all.  Projects emulated
other projects but there was no formal standard (othen than Gruber's
original doc, which was effectively frozen), and no central place to
coordinate.

FWIW https://github.com/cben/mathdown/wiki/Math-in-MarkDown has no timeline
but lists _a lot_ of implementations with _some_ math support.  Incomplete,
by this point I would not be surprised if it has less than half of
implementations out there. (It's a wiki, additions welcome!)
As any github wiki, it has git history which (very roughly) correlates with
order of appearance — but mostly the order in which I found time to
investigate them... Bias: tools I had no access to, such as Mac-only ones,
are less present and more lagging.

I don't know if Pandoc was 2nd or later with math support, but it was
certainly widely influential — it set a high bar both in breadth and
qualify of markdown extensions 👏, so I expect most people extending
markdown later, in any direction, were at least aware of it.

Some sites within Stack Exchange also adopted $math$ support (I guess
mathoverflow was the first?) which also must have been influential in the
communities using formulas.
* See my wiki, there is curious inconsistency with
electronics.stackexchange.com, they alone chose \$...\$ for inline.  Not
sure what to learn from that case, perhaps that inter-operability was
valued less than suiting particular community's situation.

Then CommonMark appeared (jgm, thank you again ;-).  While the spec itself
is focused on nailing down original syntax + few very central additions
(e.g. fenced blocks), it did provide a shared forum where people interested
in markdown can collaborate on harmonizing syntax extensions.
Math has been discussed a lot:
https://talk.commonmark.org/t/mathematics-extension/457
https://talk.commonmark.org/t/mathjax-extension-for-latex-equations/698
https://talk.commonmark.org/t/ignore-latex-like-math-mode-or-parse-it/1926
https://talk.commonmark.org/t/can-math-formula-added-to-the-markdown/3140
https://talk.commonmark.org/t/math-rendering-re-visited/4086

As for GitHub's announcement, I'm happy they're recently adopting popular
extensions (such as Mermaid), though I wish they sent some kind of "intent
to implement" on commonmark forum ahead of shipping.
Due to their weight in markdown space, any syntax they adopt is likely to
become The definite syntax...


пт, 20 мая 2022 г. в 10:28, Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>:

> GitHub recently introduced support for the `$`/`$$` Markdown math
> syntax: <https://github.blog/2022-05-19-math-support-in-markdown/>
>
> This made me wonder when and how this TeX syntax made its way into
> Markdown. I tried to dig through the history of old projects like pandoc
> and MultiMarkdown, but didn't get very far. All I could find is that
> pandoc has been supporting TeX math syntax for at least 15 years.
>
> Maybe someone here can satisfy my curiosity?
>
> --
> Albert Krewinkel
> GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124
>
> --
> You received this message because you are subscribed to the Google Groups
> "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/87pmk88xxr.fsf%40zeitkraut.de
> .
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CALJxei%2B%3D6CLro5VK9o-u2JaX46d3n8XcFtiDASOU3gUtMkOD5w%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 7568 bytes --]

  parent reply	other threads:[~2022-05-20 11:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20  7:06 Albert Krewinkel
     [not found] ` <87pmk88xxr.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-05-20 11:35   ` Beni Cherniavsky-Paskin [this message]
     [not found]     ` <CALJxei+=6CLro5VK9o-u2JaX46d3n8XcFtiDASOU3gUtMkOD5w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-05-20 11:37       ` Beni Cherniavsky-Paskin
2022-05-20 17:46   ` John Gabriele
     [not found]     ` <09be80a5-7851-4739-b1ad-1418e31d2126-jFIJ+Wc5/Vo7lZ9V/NTDHw@public.gmane.org>
2022-05-20 19:30       ` Jeremy Theler
     [not found]         ` <6d21260464c325b05285477edbb53c1f30ddbc1c.camel-24em0bpozeFWk0Htik3J/w@public.gmane.org>
2022-05-21  1:03           ` John Gabriele
2022-05-20 18:01   ` John MacFarlane

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CALJxei+=6CLro5VK9o-u2JaX46d3n8XcFtiDASOU3gUtMkOD5w@mail.gmail.com' \
    --to=beni.cherniavsky-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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 NNTP newsgroup(s).