markdown parsers (was Re: replacing static-site-generator with Tiki)

On Sun, 30 Sep 2018 19:21:45 -0400
Marc Laporte <[email protected]> wrote:

> I am optimistic that adding support for blocks of text like the
> following {COMMONMARK()} This is [an example](http://example.com/
> "Title") inline link. {COMMONMARK} will happen soon because it's very
> little work. All the heavy lifting is already done by the libs.
> 1- Add a lib from https://packagist.org/search/?tags=markdown
> 
> 2- Make a wiki plugin:
> https://dev.tiki.org/Code-Howto%3A-Create-a-Wiki-Plugin

OK, I should try how it would work with markdown-extra.

> Adding an option for page by page choice of parser is a much bigger
> project. The more we converge on fewer syntaxes, the better support
> will be.

OK.

> Which parser would you choose? From
> https://packagist.org/search/?tags=markdown

One of the most common complaints against Markdown is that it is too
simple for more serious usage and that is the reason why there are so
many flavours of markdown. Moreover, it seems that CommonMark does not
solve it.

Otoh, PHP Markdown Extra is supported by Pandoc (both reader and
writer), so, this one looks good.:

https://packagist.org/packages/michelf/php-markdown

https://michelf.ca/projects/php-markdown/extra/

https://github.com/michelf/php-markdown

although, based on
https://packagist.org/packages/erusev/parsedown-extra, several
modern CMS-es uses that extension (e.g. Grav) and it seems to be very
fast:

https://github.com/erusev/parsedown

However, one thing is clear - parser which does support Markdown Extra
and not CommonMark.


Sincerely,
Gour



-- 
Not by merely abstaining from work can one achieve freedom
from reaction, nor by renunciation alone can one attain perfection.