In 2017, GitHub released a formal specification of its GitHub Flavored Markdown (GFM) that is based on CommonMark. GitHub had been using its own variant of Markdown since as early as 2009, adding support for additional formatting such as tables and nesting block content inside list elements, as well as GitHub-specific features such as auto-linking references to commits, issues, usernames, etc.
Italic text may be implemented by _underscores_ and/or *single-asterisks*. Websites like Bitbucket, Diaspora, GitHub, OpenStreetMap, Reddit, SourceForge, and Stack Exchange use variants of Markdown to facilitate discussion between users.ĭepending on implementation, basic inline HTML tags may be supported.
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. 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.
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 ‘heavier’ markup languages, such as Rich Text Format (RTF), HTML, or even wikitext (each of which have obvious in-line tags and formatting instructions which can make the text more difficult for humans to read).
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)." In 2002 Aaron Swartz created atx and referred to it as “the true structured text format”. Markdown was inspired by pre-existing conventions for marking up plain text in email and usenet posts, such as the earlier markup languages setext (c. This was addressed in 2014, when long-standing Markdown contributors released CommonMark, an unambiguous specification and test suite for Markdown. The initial description of Markdown contained ambiguities and raised unanswered questions, causing implementations to both intentionally and accidentally diverge from the original version. Markdown is widely used in blogging, instant messaging, online forums, collaborative software, documentation pages, and readme files.
Markdown link code#
John Gruber and Aaron Swartz created Markdown in 2004 as a markup language that is appealing to human readers in its source code form. Markdown is a lightweight markup language for creating formatted text using a plain-text editor. Pandoc, MultiMarkdown, Markdown Extra, CommonMark, RMarkdown ĭaringfireball.
0 kommentar(er)
