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 blogs 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 document type definition (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. Textilebq. ) 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, reST, RD) or being converted to a certain output format (usually HTML or LaTeX) and nothing else, others are more general in application. This includes whether they are oriented on textual presentation or on data serialization.[clarification needed]
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.[26]
DokuWiki does not support HTML import natively, but HTML to DokuWiki converters and importers exist and are mentioned in the official documentation.[27] DokuWiki does not support class or id attributes, but can be set up to support HTML code, which does support both features. HTML code support was built-in before release 2023-04-04.[28] In later versions, HTML code support can be achieved through plugins, though it is discouraged.[28]
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.
Gemtext does not have any inline formatting, monospaced text (called preformatted text in the context of Gemtext) must have the opening and closing ``` on their own lines.
Emphasis syntax
In HTML, text is emphasized with the <em> and <strong> element types, whereas <i> and <b> traditionally mark up text to be italicized or bold-faced, respectively.
Microsoft Word and Outlook, and accordingly other word processors and mail clients that strive for a similar user experience, support the basic convention of using asterisks for boldface and underscores for italic style. While Word removes the characters, Outlook retains them.
Italic type or normal emphasis
Code
AsciiDoc
ATX
Creole, DokuWiki
Jira
Markdown
MediaWiki
Org-mode
PmWiki
reST
Setext
Slack
Textile
Texy!
TiddlyWiki
txt2tags
WhatsApp
*italic*
No
No
No
No
Yes
No
No
No
Yes
No
No
No
Yes
No
No
No
**italic**
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
_italic_
Yes
Yes
No
Yes
Yes
No
No
No
No
No
Yes
Yes
No
No
No
Yes
__italic__
Yes
No
No
No
No
No
No
No
No
No
No
Yes
No
No
No
No
'italic'
Yes
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
''italic''
Yes
No
No
No
No
Yes
No
Yes
No
No
No
No
No
No
No
No
/italic/
No
No
No
No
No
No
Yes
No
No
No
No
No
No
No
No
No
//italic//
No
No
Yes
No
No
No
No
No
No
No
No
No
Yes
Yes
Yes
No
~italic~
No
No
No
No
No
No
No
No
No
Yes
No
No
No
No
No
No
Bold face or strong emphasis
Code
AsciiDoc
ATX
Creole, DokuWiki
Jira
Markdown
MediaWiki
Org-mode
PmWiki
reST
Setext
Slack
Textile
Texy!
TiddlyWiki
txt2tags
WhatsApp
*bold*
Yes
Yes
No
Yes
No
No
Yes
No
No
No
Yes
Yes
No
No
No
Yes
**bold**
Yes
No
Yes
No
Yes
No
No
No
Yes
Yes
No
Yes
Yes
No
Yes
No
__bold__
No
No
No
No
Yes
No
No
No
No
No
No
No
No
No
No
No
''bold''
No
No
No
No
No
No
No
No
No
No
No
No
No
Yes
No
No
'''bold'''
No
No
No
No
No
Yes
No
Yes
No
No
No
No
No
No
No
No
Editorial syntax
In HTML, removed or deleted and inserted text is marked up with the <del> and <ins> element types, respectively. However, legacy element types <s> or <strike> and <u> are still also available for stricken and underlined spans of text.
Underlined or inserted text
Code
DokuWiki
Jira
Markdown
Org-mode
Setext
TiddlyWiki
txt2tags
_underline_
No
No
Optional
Yes
Yes
No
No
__underline__
Yes
No
Optional
No
No
Yes
Yes
+underline+
No
Yes
No
No
No
No
No
AsciiDoc, ATX, Creole, MediaWiki, PmWiki, reST, Slack, Textile, Texy! and WhatsApp do not support dedicated markup for underlining text. Textile does, however, support insertion via the +inserted+ syntax.
Strike-through or deleted text
Code
Jira
Markdown
Org-mode
Slack
Textile
TiddlyWiki
txt2tags
WhatsApp
~stricken~
No
No
No
Yes
No
No
No
Yes
~~stricken~~
No
GFM
No
No
No
Yes
No
No
+stricken+
No
No
Yes
No
No
No
No
No
-stricken-
Yes
No
No
No
Yes
No
No
No
--stricken--
No
No
No
No
No
No
Yes
No
AsciiDoc, ATX, Creole, MediaWiki, PmWiki, reST, Setext and Texy! do not support dedicated markup for striking through text.
DokuWiki supports HTML-like <del>stricken</del> syntax, even with embedded HTML disabled.
Programming syntax
Quoted computer code is traditionally presented in typewriter-like fonts where each character occupies the same fixed width. HTML offers the semantic <code> and the deprecated, presentational <tt> element types for this task.
Monospaced font, teletype text or code
Code
AsciiDoc
ATX
Creole
Gemtext
Jira
Markdown
Org-mode
PmWiki
reST
Slack
Textile
Texy!
TiddlyWiki
txt2tags
WhatsApp
@code@
No
No
No
No
No
No
No
No
No
No
Yes
No
No
No
No
@@code@@
No
No
No
No
No
No
No
Yes
No
No
No
No
No
No
No
`code`
Yes
No
No
No
No
Yes
No
No
No
Yes
No
Yes
Yes
No
No
``code``
Yes
No
No
No
No
Yes
No
No
Yes
No
No
No
Yes
Yes
No
```code```
No
No
No
Yes
No
Yes
No
No
No
Yes/No
No
No
Yes
No
Yes
=code=
No
No
No
No
No
No
Yes
No
No
No
No
No
No
No
No
~code~
No
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
No
++code++
Yes
No
No
No
No
No
No
No
No
No
No
No
No
No
No
{{code}}
No
No
No
No
Yes
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
No
|code|
No
Yes
No
No
No
No
No
No
No
No
No
No
No
No
No
;;code;;
Mediawiki and Gemtext do not provide lightweight markup for inline code spans.
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[50] 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.
RST determines 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.
Microsoft Word supports auto-formatting paragraphs as headings if they do not contain more than a handful of words, no period at the end and the user hits the enter key twice. For lower levels, the user may press the tabulator key the according number of times before entering the text, i.e. one through eight tabs for heading levels two through nine.
Link syntax
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.
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>
TiddlyWiki
[[Text|http://example.com]]
Jira
[http://example.com]
[Text|http://example.com]
txt2tags
[Text http://example.com]
MediaWiki
[http://example.com Text]
Creole, MediaWiki, PmWiki, DokuWiki
[[Name]]
[[Name|Text]]
Org-mode
[[Name][Text]]
TiddlyWiki
[[Text|Name]]
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/>`_
setext
^.. _Link_name URL
POD
L<http://example.com/>
L</Name>
Gemtext
=> gemini://example.com
=> gemini://example.com Text
Gemtext and setext links must be on a line by themselves, they cannot be used inline.
Org-mode's normal link syntax does a text search of the file. You can also put in dedicated targets with <<id>>.
List syntax
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.
Microsoft Word automatically converts paragraphs that start with an asterisk *, hyphen-minus - or greater-than bracket > followed by a space or horizontal tabulator as bullet list items. It will also start an enumerated list for the digit 1 and the case-insensitive letters a (for alphabetic lists) or i (for roman numerals), if they are followed by a period ., a closing round parenthesis ), a greater-than sign > or a hyphen-minus - and a space or tab; in case of the round parenthesis an optional opening one ( before the list marker is also supported.
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 respect a start value other than 1, but ignore any other explicit value.
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.
The following lightweight markup languages, while similar to some of those already mentioned, have not yet been added to the comparison tables in this article:
^Footnote in official manual "When using ‘*’ as a bullet, lines must be indented so that they are not interpreted as headlines. Also, when you are hiding leading stars to get a clean outline view, plain list items starting with a star may be hard to distinguish from true headlines. In short: even though ‘*’ is supported, it may be better to not use it for plain list items."
