![rich text vs markdown rich text vs markdown](https://developer.appway.com/filesystem/f3c92cb40240b8bbbc2fe60d7acb9f9715244998351cc22d448cbe5d62e53726/markdown_vs_bbcode.png)
A community website now aims to "document various tools and resources available to document authors and developers, as well as implementors of the various Markdown implementations". Standardization CommonMarkįrom 2012, a group of people, including Jeff Atwood and John MacFarlane, launched what Atwood characterised as a standardisation effort. Gruber avoided using curly braces in Markdown to unofficially reserve them for implementation-specific extensions. However, Gruber has argued that complete standardization would be a mistake: "Different sites (and people) have different needs. These issues spurred the creation of tools such as Babelmark to compare the output of various implementations, and an effort by some developers of Markdown parsers for standardisation. The behavior of some of these diverged from the reference implementation, as Markdown was only characterised by an informal specification and a Perl implementation for conversion to HTML.Īt the same time, a number of ambiguities in the informal specification had attracted attention. Rise and divergence Īs Markdown's popularity grew rapidly, many Markdown implementations appeared, driven mostly by the need for additional features such as tables, footnotes, definition lists, and Markdown inside HTML blocks.
![rich text vs markdown rich text vs markdown](https://support.airtable.com/hc/article_attachments/360061110613/mceclip2.png)
![rich text vs markdown rich text vs markdown](https://www.appsntips.com/content/images/2020/06/Scrivener-vs-Ulysses---Exporting---Ulysses-1.jpg)
It can take the role of a standalone script, a plugin for Blosxom or a Movable Type, or of a text filter for BBEdit. Gruber wrote a Perl script,, which converts marked-up text input to valid, well-formed XHTML or HTML and replaces angle brackets ( ) and ampersands ( &) with their corresponding character entity references. To this end, its main inspiration is the existing conventions for marking up plain text in email, though it also draws from earlier markup languages, notably setext, Textile, and reStructuredText. Its key design goal was readability, that the language be readable as-is, without looking like it has been marked up with tags or formatting instructions, unlike text formatted with a markup language, such as Rich Text Format (RTF) or HTML, which have obvious tags and formatting instructions. In 2002 Aaron Swartz created atx, "the true structured text format.” Swartz and Gruber then worked together to create the Markdown language in 2004, with the goal of enabling people "to write using an easy-to-read and easy-to-write plain text format, optionally convert it to structurally valid XHTML (or HTML)."