Comparison of lightweight markup language syntax Heading syntax Underlined headings Prefixed headings Link syntax Image syntax List syntax Quotation syntax Table syntax
See also
References
External links
A lightweight markup language (LML), also termed a simple or humane markup language, is a markup language with simple, unobtrusive syntax. It is designed to be easy to write using any generic text editor and easy to read in its raw form. Lightweight markup languages are used in applications where it may be necessary to read the raw document as well as the final rendered output.
For instance, a person downloading a software library might prefer to read the documentation in a text editor rather than a web browser. Another application for such languages is to provide for data entry in web-based publishing, such as weblogs and wikis, where the input interface is a simple text box. The server software then converts the input into a common document markup language like HTML.
History
Lightweight markup languages were originally used on text-only displays which could not display characters in italics or bold, so informal methods to convey this information had to be developed. This formatting choice was naturally carried forth to plain-text email communications. Console browsers may also resort to similar display conventions.
In 1986 international standard SGML provided facilities to define and parse lightweight markup languages using grammars and tag implication. The 1998 W3C XML is a profile of SGML that omits these facilities. However, no SGML DTD for any of the languages listed below is known.
Types
Lightweight markup languages can be categorized by their tag types. Like HTML (<b>bold</b>), some languages use named elements that share a common format for start and end tags (e.g. BBCode [b]bold[/b]), whereas proper lightweight markup languages are restricted to ASCII-only punctuation marks and other non-letter symbols for tags, but some also mix both styles (e.g. Textile bq. ) or allow embedded HTML (e.g. Markdown), possibly extended with custom elements (e.g. MediaWiki <ref>source</ref>).
Most languages distinguish between markup for lines or blocks and for shorter spans of texts, but some only support inline markup.
Some markup languages are tailored for a specific purpose, such as documenting computer code (e.g. POD, RD) or being converted to a certain output format (usually HTML) and nothing else, others are more general in application. This includes whether they are oriented on textual presentation or on data serialization.{{clarify|date=June 2014}}
Presentation oriented languages include AsciiDoc, atx, BBCode, Creole, Crossmark, Epytext, Haml, JsonML, MakeDoc, Markdown, Org-mode, POD, reST, RD, Setext, SiSU, SPIP, Xupl, Texy!, Textile, txt2tags, UDO and Wikitext.
Data serialization oriented languages include Curl (homoiconic, but also reads JSON; every object serializes), JSON, OGDL, and YAML.
Comparison of language features
Comparing language features
Language
HTML export tool
HTML import tool
Tables
Link titles
class attribute
id attribute
Release date
AsciiDoc
{{yes}}
{{yes}}
{{yes}}
{{yes}}
{{yes}}
{{yes}}
November 25, 2002[1]
BBCode
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
1998
Creole
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
July 4, 2007[2]
GitHub Flavored Markdown
{{yes}}
{{no}}
{{yes}}
{{yes}}
{{no}}
{{no}}
?
Markdown
{{yes}}
{{yes}}
{{no}}
{{yes}}
{{yes-no}}
{{yes-no}}
March 19, 2004[3][4]
Markdown Extra
{{yes}}
{{yes}}
{{yes}}[5]
{{yes}}
{{yes}}
{{yes}}
?
MediaWiki
{{yes}}
{{yes}}
{{yes}}
{{yes}}
{{yes}}
{{yes}}
2002[6]
MultiMarkdown
{{yes}}
{{no}}
{{yes}}
{{yes}}
{{no}}
{{no}}
?
Org-mode
{{yes}}
{{yes}}[7]
{{yes}}
{{yes}}
{{yes}}
{{yes}}
2003[8]
PmWiki
{{yes}}[9]
{{yes}}
{{yes}}
{{yes}}
{{yes}}
{{yes}}
January, 2002
POD
{{yes}}
{{dunno}}
{{no}}
{{yes}}
{{dunno}}
{{dunno}}
1994
reStructuredText
{{yes}}
{{yes}}[7]
{{yes}}
{{yes}}
{{yes}}
auto}}
April 2, 2002[10]
Textile
{{yes}}
{{no}}
{{yes}}
{{yes}}
{{yes}}
{{yes}}
December 26, 2002[11]
Texy
{{yes}}
{{yes}}
{{yes}}
{{yes}}
{{yes}}
{{yes}}
2004[12]
txt2tags
{{yes}}
{{yes}}[13]
{{yes}}[14]
{{yes}}
{{yes-no}}
{{yes-no}}
July 26, 2001[15]
Slack
{{no}}
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
[16][17]
WhatsApp
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
March 16, 2016[18]
Markdown's own syntax does not support class attributes or id attributes; however, since Markdown supports the inclusion of native HTML code, these features can be implemented using direct HTML. (Some extensions may support these features.)
txt2tags' own syntax does not support class attributes or id attributes; however, since txt2tags supports inclusion of native HTML code in tagged areas, these features can be implemented using direct HTML when saving to an HTML target.[19]
Comparison of implementation features
Comparing implementations, especially output formats
Although usually documented as yielding italic and bold text, most lightweight markup processors output semantic HTML elements em and strong instead. Monospaced text may either result in semantic code or presentational tt elements. Few languages make a distinction, e.g. Textile, or allow the user to configure the output easily, e.g. Texy.
LMLs sometimes differ for multi-word markup where some require the markup characters to replace the inter-word spaces (infix).
Some languages require a single character as prefix and suffix, other need doubled or even tripled ones or support both with slightly different meaning, e.g. different levels of emphasis.
Comparing text formatting syntax
HTML output
<strong>strongly emphasized</strong>
<em>emphasized text</em>
<code>code</code>
semantic
<b>bold text</b>
<i>italic text</i>
<tt>monospace text</tt>
presentational
AsciiDoc
*bold text*
'italic text'
+monospace text+
Can double operators to apply formatting where there is no word boundary (for example **b**old t**ex**t yields bold text).
_italic text_
`monospace text`
ATX
*bold text*
_italic text_
>monospace text|
email style
Creole
**bold text**
//italic text//
{{{monospace text}}}
Triple curly braces are for nowiki which is optionally monospace.
Markdown[39]
**bold text**
*italic text*
`monospace text`
semantic HTML tags
__bold text__
_italic text_
MediaWiki
'''bold text'''
''italic text''
<code>monospace text</code>
mostly resorts to inline HTML
Org-mode
*bold text*
/italic text/
=code=
~verbatim~
PmWiki
'''bold text'''
''italic text''
@@monospace text@@
reST
**bold text**
*italic text*
``monospace text``
Setext
**bold text**
~italic text~
{{N/A}}
Textile[40]
*strong*
_emphasis_
@monospace text@
semantic HTML tags
**bold text**
__italic text__
presentational HTML tags
Texy!
**bold text**
*italic text*
`monospace text`
semantic HTML tags by default, optional support for presentational tags
//italic text//
txt2tags
**bold text**
//italic text//
``monospace text``
POD
B<bold text>
I<italic text>
C<monospace text>
Indented text is also shown as monospaced code.
BBCode
[b]bold text[/b]
[i]italic text[/i]
[code]monospace text[/code]
Formatting works across line breaks.
Slack
*bold text*
_italic text_
`monospace text`
```block of monospaced text```
WhatsApp
*bold text*
_italic text_
```monospace text```
Bold face or strong emphasis
Code
AsciiDoc
ATX
Creole
Markdown
MediaWiki
Org-mode
PmWiki
reST
Setext
Slack
Textile
Texy!
txt2tags
WhatsApp
*bold*
{{yes}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{yes}}
{{yes}}
{{no}}
{{no}}
{{yes}}
**bold**
{{yes}}
{{no}}
{{yes}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{yes}}
{{yes}}
{{no}}
{{yes}}
{{yes}}
{{yes}}
{{no}}
__bold__
{{no}}
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
'''bold'''
{{no}}
{{no}}
{{no}}
{{no}}
{{yes}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
Italic type or normal emphasis
Code
AsciiDoc
ATX
Creole
Markdown
MediaWiki
Org-mode
PmWiki
reST
Setext
Slack
Textile
Texy!
txt2tags
WhatsApp
*italic*
{{no}}
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
**italic**
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
_italic_
{{yes}}
{{yes}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{yes}}
{{yes}}
{{no}}
{{no}}
{{yes}}
__italic__
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
'italic'
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
''italic''
{{yes}}
{{no}}
{{no}}
{{no}}
{{yes}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
/italic/
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
//italic//
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{yes}}
{{yes}}
{{no}}
~italic~
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
Underlined text
Code
AsciiDoc
ATX
Creole
Markdown
MediaWiki
Org-mode
PmWiki
reST
Setext
Slack
Textile
Texy!
txt2tags
WhatsApp
_underline_
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
__underline__
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{yes}}
{{no}}
Strike-through text
Code
AsciiDoc
ATX
Creole
Markdown
MediaWiki
Org-mode
PmWiki
reST
Setext
Slack
Textile
Texy!
txt2tags
WhatsApp
~stricken~
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{yes}}
~~stricken~~
{{no}}
{{no}}
{{no}}
GFM}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
+stricken+
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
--stricken--
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{yes}}
{{no}}
Monospaced font, teletype text or code
Code
AsciiDoc
ATX
Creole
Markdown
MediaWiki
Org-mode
PmWiki
reST
Setext
Slack
Textile
Texy!
txt2tags
WhatsApp
@code@
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
@@code@@
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
`code`
{{yes}}
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{yes}}
{{no}}
{{yes}}
{{no}}
{{no}}
``code``
{{yes}}
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{yes}}
{{no}}
```code```
{{no}}
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{yes-no}}
{{no}}
{{no}}
{{no}}
{{yes}}
=code=
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
~code~
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
+code+
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
++code++
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{{code
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
>code|
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
Heading syntax
Headings are usually available in up to six levels, but the top one is often reserved to contain the same as the document title, which may be set externally. Some documentation may associate levels with divisional types, e.g. part, chapter, section, article or paragraph.
Most LMLs follow one of two styles for headings, either Setext-like underlines or atx-like[41] line markers, or they support both.
The first style uses underlines, i.e. repeated characters (e.g. equals =, hyphen - or tilde ~, usually at least two or four times) in the line below the heading text.
Underlined heading levels
Chars:
=
-
~
*
#
+
^
_
:
”
’
`
<
>
min
Markdown
1}}
2}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
1
Setext
1}}
2}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{dunno}}
AsciiDoc
1}}
2}}
3}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
2
Texy!
{{yes}}
{{yes}}
{{no}}
{{yes}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{dunno}}
reStructuredText
{{yes}}
{{yes}}
{{yes}}
{{yes}}
{{yes}}
{{yes}}
{{yes}}
{{yes}}
{{yes}}
{{yes}}
{{yes}}
{{yes}}
{{yes}}
{{yes}}
heading width
RST and Texy determine heading levels dynamically, which makes authoring more individual on the one hand, but complicates merges from external sources on the other hand.
The second style is based on repeated markers (e.g. hash #, equals = or asterisk *) at the start of the heading itself, where the number of repetitions indicates the (sometimes inverse) heading level. Most languages also support the reduplication of the markers at the end of the line, but whereas some make them mandatory, others do not even expect their numbers to match.
Line prefix (and suffix) headings
Character:
=
#
*
!
+
Suffix
Levels
Indentation
AsciiDoc
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{optional}}
1–6
{{no}}
ATX
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
unlimited
{{dunno}}
Creole
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{optional}}
1–6
{{no}}
MediaWiki
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{yes}}
1–6
{{no}}
txt2tags
{{yes}}
{{no}}
{{no}}
{{no}}
{{yes}}
{{yes}}
1–6
{{no}}
Markdown
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{optional}}
1–6
{{no}}
Texy!
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{optional}}
6–1 or 1–6, dynamic
{{no}}
Org-mode
{{no}}
{{no}}
{{yes}}
{{no}}
{{no}}
{{no}}
1– +∞
alternative}}[42][43]
PmWiki
{{no}}
{{no}}
{{no}}
{{yes}}
{{no}}
{{optional}}
1–6
{{no}}
POD and Textile choose the HTML convention of numbered heading levels instead.
Org-mode supports indentation as a means of indicating the level.
Hyperlinks can either be added inline, which may clutter the code because of long URLs, or with named alias or numbered id references to lines containing nothing but the address and related attributes and often may be located anywhere in the document.
Most languages allow the author to specify text Text to be displayed instead of the plain address http://example.com and some also provide methods to set a different link title Title which may contain more information about the destination.
LMLs that are tailored for special setups, e.g. wikis or code documentation, may automatically generate named anchors (for headings, functions etc.) inside the document, link to related pages (possibly in a different namespace) or provide a textual search for linked keywords.
Most languages employ (double) square or angular brackets to surround links, but hardly any two languages are completely compatible. Many can automatically recognize and parse absolute URLs inside the text without further markup.
Inline hyperlink syntax
Languages
Basic syntax
Text syntax
Title syntax
BBCode, Creole, MediaWiki, PmWiki
http://example.com
Textile
"Text":http://example.com
"Text (Title)":http://example.com
Texy!
"Text .(Title)":http://example.com
AsciiDoc
http://example.com[Text]
Slack
<http://example.com>Text>
txt2tags
[http://example.com]
[Text http://example.com]
MediaWiki
[http://example.com Text]
Creole, MediaWiki, PmWiki
[[Name]]
[[Name>Text]]
Org-mode
[[Name][Text]]
Creole
[[Namespace:Name]]
[[Namespace:Name>Text]]
Org-mode
[[Namespace:Name][Text]]
Creole, PmWiki
[[http://example.com]]
[[http://example.com>Text]]
BBCode
[url]http://example.com[/url]
[url=http://example.com]Text[/url]
Markdown
<http://example.com>
[Text](http://example.com)
[Text](http://example.com "Title")
reStructuredText
`Text <http://example.com/>`_
POD
L</Name>
POD
L<http://example.com/>
Reference syntax
Languages
Text syntax
Title syntax
reStructuredText
ATX
AsciiDoc
Markdown
Org-mode
Org-mode's normal link syntax does a text search of the file. You can also put in dedicated targets with <>.
HTML requires an explicit element for the list, specifying its type, and one for each list item, but most lightweight markup languages need only different line prefixes for the bullet points or enumerated items. Some languages rely on indentation for nested lists, others use repeated parent list markers.
Unordered, bullet list items
Characters:
*
-
+
#
.
·
•
_
:
–
—
indent
skip
nest
Markdown
{{yes}}
{{yes}}
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
0–3
1–3
indent
MediaWiki
{{yes}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
0
1+
repeat
Languages differ on whether they support optional or mandatory digits in numbered list items, which kinds of enumerators they understand (e.g. decimal digit 1, roman numerals i or I, alphabetic letters a or A) and whether they support to keep explicit values in the output format. Some Markdown dialects, for instance, will honor a start value other than 1, but ignore any other explicit value.
Ordered, enumerated list items
Chars:
#1
1.
1)
1]
1}
(1)
[1]
{1}
indent
skip
nest
Markdown
{{no}}
1}}
1}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
0–3
1–3
indent
MediaWiki
#}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
{{no}}
0
1+
repeat
Slack assists the user in entering enumerated and bullet lists, but does not actually format them as such, i.e. it just includes a leading digit followed by a period and a space or a bullet character • in front of a line.
See also
Comparison of document markup languages
Comparison of documentation generators
WikiText
Markdown
References
1. ^{{cite web|url=http://asciidoc.org/CHANGELOG.html |title=AsciiDoc ChangeLog |accessdate=2017-02-24}} 2. ^{{cite web|url=http://www.wikicreole.org/wiki/Versions |title=WikiCreole Versions |accessdate=2017-02-24}} 3. ^{{cite web |url=http://www.aaronsw.com/weblog/001189 |title=Markdown |date=2004-03-19 |work=Aaron Swartz: The Weblog}} 4. ^{{cite web |url=http://daringfireball.net/projects/markdown/ |archiveurl=https://web.archive.org/web/20040402182332/http://daringfireball.net/projects/markdown/ |archivedate=2004-04-02 |title=Daring Fireball: Markdown |accessdate=2014-04-25}} 5. ^{{cite web|url=http://michelf.com/projects/php-markdown/extra/#table |title=PHP Markdown Extra |publisher=Michelf.com |date= |accessdate=2013-10-08}} 6. ^{{cite web|url=https://www.mediawiki.org/wiki/MediaWiki_history |title=MediaWiki history |accessdate=2017-02-24}} 7. ^1 2 Pandoc, which is written in Haskell, parses Markdown (in two forms) and ReStructuredText, as well as HTML and LaTeX; it writes from any of these formats to HTML, RTF, LaTeX, ConTeXt, OpenDocument, EPUB and several other formats, including (via LaTeX) PDF. 8. ^{{cite web |url=http://orgmode.org/ |title=Org mode for Emacs – Your Life in Plain Text |website=orgmode.org |publisher=OrgMode team |accessdate=2016-12-09}} 9. ^{{cite web|url=http://www.pmwiki.org/wiki/PmWiki/Cookbook?action=search&q=name%3DXmlExport%2CBackupHTMLZip%2CExportHTML*%2CPrintGroup+list%3Dmain|title=PmWiki Cookbook - Export addons|accessdate=7 January 2018}} 10. ^{{cite web|url=http://docutils.sourceforge.net/docs/ref/rst/introduction.html#history |title=An Introduction to reStructuredText |accessdate=2017-02-24}} 11. ^{{cite web|url=http://textism.com/tools/textile/|archiveurl=https://web.archive.org/web/20021226035527/http://textism.com/tools/textile/|title=Textism › Tools › Textile|archivedate=26 December 2002|work=textism.com}} 12. ^{{cite web|url=https://texy.info/en/ |title=What is Texy |accessdate=2017-02-24}} 13. ^{{cite web|url=https://metacpan.org/pod/HTML::WikiConverter::Txt2tags |title=Html2wiki txt2tags module|publisher=cpan.org |date= |accessdate=2014-01-30}} 14. ^{{cite web|url=http://txt2tags.org/userguide/Table.html#6_14 |title=Txt2tags User Guide | publisher=Txt2tags.org |date= |accessdate=2017-02-24}} 15. ^{{cite web|url=http://txt2tags.org/changelog.html |title=txt2tags changelog |accessdate=2017-02-24}} 16. ^{{cite web|url=https://get.slack.help/hc/en-us/articles/202288908 |title= Slack Help Center > Using Slack > Send messages > Format your messages |accessdate=2018-08-07}} 17. ^{{cite web|url=https://api.slack.com/docs/message-formatting |title= Slack API documentation: Basic message formatting |accessdate=2018-08-07}} 18. ^{{cite web|url=https://faq.whatsapp.com/en/android/26000002/ |title=WhatsApp FAQ: Formatting your messages|accessdate=2017-11-21}} 19. ^{{cite web|url=http://txt2tags.org/userguide/TaggedTaggedLineTaggedArea.html#6_16 |title=Txt2tags User Guide | publisher=Txt2tags.org |date= |accessdate=2017-02-24}} 20. ^{{cite web|url=http://www.wikicreole.org/wiki/Converters |title=Converters |publisher=WikiCreole |date= |accessdate=2013-10-08}} 21. ^[https://github.com/sirthias/pegdown pegdown]: A Java library for Markdown processing 22. ^1 [https://github.com/ypocat/gfms gfms]: Github Flavored Markdown Server 23. ^1 [https://github.com/chjj/marked marked]: A full-featured markdown parser and compiler, written in JavaScript. Built for speed. 24. ^1 [https://github.com/gagle/Node-GFM node-gfm]: GitHub flavored markdown to HTML converter 25. ^Parsedown: Markdown parser written in PHP 26. ^1 [https://github.com/kzykhys/Ciconia Ciconia]: Markdown parser written in PHP 27. ^1 [https://github.com/joeyespo/grip Grip]: GitHub Readme Instant Preview 28. ^[https://rubygems.org/gems/github-markdown github-markdown]: Self-contained Markdown parser for GitHub 29. ^[https://github.com/jgm/peg-markdown peg-markdown] is an implementation of markdown in C. 30. ^Discount is also an implementation of markdown in C. 31. ^{{cite web|url=https://github.com/waylan/Python-Markdown |title=Python-Markdown |publisher=Github.com |date= |accessdate=2013-10-08}} 32. ^{{cite web|author=Bruce Williams , for Ruby Central |url=https://rubyforge.org/projects/kramdown/ |title=kramdown: Project Info |publisher=RubyForge |date= |accessdate=2013-10-08 |deadurl=yes |archiveurl=https://web.archive.org/web/20130807011316/http://rubyforge.org/projects/kramdown |archivedate=2013-08-07 |df= }} 33. ^1 {{cite web|url=https://github.com/kawabata/ox-pandoc#description |title=Via ox-pandoc and pandoc itself}} 34. ^{{cite web | last=Atlassian | title=Confluence 4.0 Editor - What's Changed for Wiki Markup Users (Confluence Wiki Markup is dead) | url=https://confluence.atlassian.com/display/CONF40/Confluence+4+Editor+-+What%27s+Changed+for+Wiki+Markup+Users | accessdate=2018-03-28}} 35. ^Docutils is an implementation of ReStructuredText in Python 36. ^Sphinx is an implementation of ReStructuredText in Python and Docutils with a number of output format Builders 37. ^{{cite web|author=Aurelio Jargas www.aurelio.net |url=http://txt2tags.org/ |title=txt2tags |publisher=txt2tags |date=2012-01-11 |accessdate=2013-10-08}} 38. ^{{cite web|url=http://txt2tags.org/txt2tags.form.php |title=txt2tags.class.php - online convertor [sic] |publisher=Txt2tags.org |date= |accessdate=2013-10-08}} 39. ^{{cite web|url=http://daringfireball.net/projects/markdown/syntax |title=Markdown Syntax |publisher=Daringfireball.net |date= |accessdate=2013-10-08}} 40. ^1 Textile Syntax {{webarchive|url=https://web.archive.org/web/20100812131431/http://textile.thresholdstate.com/ |date=2010-08-12 }} 41. ^"atx, the true structured text format" by Aaron Swartz (2002) 42. ^{{cite web|url=http://lists.gnu.org/archive/html/emacs-orgmode/2009-07/msg00651.html |title=using org-adapt-indentation}} 43. ^{{cite web|url=http://emacs.stackexchange.com/questions/3786/indented-multi-tiered-lists-and-headings-with-org-indent-mode |title=using org-indent-mode or org-indent}}
External links
{{wikibooks|Curl}}
C2's list
Curl Markup to replace HTML+CSS+JS
Inhabitants of the authoring ecosphere
List at otl website
Humane Text Formats - A comparison (obsolete)
Pandoc: a versatile inter-format converter
{{Markup languages}}Auszeichnungssprache#Lightweight Markup Language