Alexandre ZANNI

Rather than changing the name (breaking change) just create an alias.

Something like this I guess, ```json {[ {"Contest":"A", "Date":"B", "Location":"C"}, {"Contest":"D", "Date":"E", "Location":"F"}, {"Contest":"G", "Date":"H", "Location":"I"} ]} ```

Yeah if you want to be strict about Markdown syntax using commonmark, the path is to enable it via extensions.

I described the idea in details here: https://github.com/intuit/Ignite/issues/126

~~Seems related to https://bugs.archlinux.org/task/71007~~ Updated to mono 6.13.0

@hbbio what's up with the chat in docker?

Some programming languages have a native library for parsing JSON but not XML, forcing the dev to install, maintain compatibility, and update dependencies with an external library.

> Are you aware of https://pygments.org/docs/lexers/? Yes but this is not concise and people will look for `pygments languages supports` on search engines or click on the `languages` button from...

Keeping the two pages sounds good too. Only name and aliases which is easy and concise to read for end user that just want to know which keyword use above...

Nice work for https://pygments.org/languages/ !