[applicative]

Pandoc’s specific markdown has had these for 20 years. They are from latex itself not mathjax. You’d think the list would have talked him out of it if it was a problem. What legit use of $ as ‘dollar’ is missed by this spec?

> 8.13.1 Extension: tex_math_dollars

> Anything between two $ characters will be treated as TeX math. The opening $ must have a non-space character immediately to its right, while the closing $ must have a non-space character immediately to its left, and must not be followed immediately by a digit. Thus, $20,000 and $30,000 won’t parse as math. If for some reason you need to enclose text in literal $ characters, backslash-escape them and they won’t be treated as math delimiters.

[joesuf4]

Naive, and cloistered. Not a great look. Maybe 5 people and their friends use Pandoc, so it doesn’t have to be robust.

[applicative]

==> pandoc : stable 3.9.0.2 (bottled), HEAD

Swiss-army knife of markup format conversion

https://pandoc.org/

Installed (on request)

From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/...

License: GPL-2.0-or-later

==> Installed Kegs and Versions

pandoc 3.9.0.2 (11 files, 274.7MB) [Linked]

==> Dependencies

Required (1): gmp

Recursive Runtime (1): all installed

==> Analytics

install: 31,898 (30 days), 119,598 (90 days), 369,388 (365 days)

[joesuf4]

Yawn. Nobody uses it to parse GFM unless they are over 60.

[applicative]

It is used almost entirely with gfm, the operation of gfm was in consultation. it was in this connection that the commonmark specification was formulated.

[joesuf4]

Seven years ago? Who cares?

[apnorton]

> Maybe 5 people and their friends use Pandoc

The pandoc repository[1] has nearly 45k stars and 4k forks. It's embedded in Jupyter notebooks, which are used by data scientists the world over. The python wrapper for pandoc has 16 million downloads[2].

[1]: https://github.com/jgm/pandoc [2]: https://pypi.org/project/pandoc/

[joesuf4]

Great, but Jupyter notebooks aren’t written in Markdown.

Next?

[apnorton]

They are, though. [1]

But maybe that's insufficient. Hugo[2], one of the most widespread static site generators in existence, supports Pandoc markdown flavors as well as general GFM.[3]

[1]: https://jupyter-notebook.readthedocs.io/en/stable/examples/N...

[2]: https://github.com/gohugoio/hugo

[3]: https://gohugo.io/content-management/formats/

[joesuf4]

They are not supported by GitHub’s GFM, and you are being incredibly bad faith about this fact.

If you are comfortable calling Markdown a futile exercise in avoiding proprietary control of a universal, simple document format for wide interoperability across natural languages, programming languages, and monopoly interests, then you and I are Microsoft vs Sun over Java in the 1990s.

[applicative]

The original Gruber-Shwartz format, which is in fact fundamentally a perl program attached to a brief expression of its intention, is not used by anyone except those who still use the perl program. Every other implementation avoids thousands of corner cases present in the perl, while of course producing its own.

[joesuf4]

If it really was this simple GitHub would have publicized this spec instead of being intentionally vague and opaque about it.

But you know what’s best.

[applicative]

The spec is the commonmark spec together with extensions of the type the commonmark spec was devised to make possible. People know better than to leave such a 'language' with a 'spec' that only really resides in a perl program, of all things. There are lists upon lists upon lists of corner cases the the perl does differently from every other program that, in the first years, reimplemented it. All of them show the perl does not meet the intention.

[joesuf4]

You are such a bore. Read the motivating preamble in Gruber's spec- that's the part the GFM standardization process stayed faithful to.

Up until Microsoft got involved.