Lightweight markup language
From Wikipedia, the free encyclopedia
This article may require cleanup to meet Wikipedia's quality standards. Please improve this article if you can. (December 2007) |
A lightweight markup language is a markup language with a simple syntax, designed to be easy for a human to enter with a simple text editor, and easy to read in its raw form.
Lightweight markup languages are used in applications where people might be expected to read the document source as well as the rendered output. For instance, a person downloading a software library might prefer to read the documentation in a text editor rather than a browser.
Another application is for entry in web-based publishing, such as weblogs and wikis, where the input interface is a simple text box. The server software converts the input to a common document markup language like HTML or XHTML.
Contents |
[edit] 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.
[edit] List of lightweight markup languages
The following is a partial list of lightweight markup languages.
[edit] Presentation oriented
- Almost Free Text ([1])
- Almost Plain Text ([2])
- AsciiDoc ([3])
- atx (markup language) ([4])
- BBCode
- BlogMe ([5])
- Creole (proposed common wiki markup)
- CrossMark
- Deplate ([6])
- Epytext ([7])
- EtText ([8])
- Grutatext ([9])
- Haml ([10])
- jemdoc ([11])
- JsonML ([12])
- Markdown ([13])
- WakabaMark ([14])
- Muse Mode ([15]) of Emacs
- o7aCode ([16])
- Pandoc ([17])
- Perl Text To HTML ([18])
- POD
- reStructuredText ([19])
- Ruby Document format
- Setext ([20])
- SiSU ([21])
- Skribe ([22])
- Spip ([23])
- Structured text
- Stx2any([24])
- Texy! ([25])
- Textile
- Terence's Markup Language ([26])
- txt2tags ([27])
- UDO ([28])
- Wikitext
- Xilize ([29])
- Yodl ([30])
[edit] Data serialization oriented
[edit] Comparison of lightweight markup language syntax
[edit] Text/font-face formatting
Language | Bold | Italic | Monospace (teletype) | Notes | |
---|---|---|---|---|---|
Almost Free Text | _bold text_ |
''italic text'' |
|monospace text| |
Formatting will not occur across line breaks unless the first formatting character is the first character on the line. | |
BBCode | [b]bold text[/b] |
[i]italic text[/i] |
[code]monospace text[/code] |
Formatting works across line breaks. | |
Creole | **bold text** |
//italic text// |
{{{monospace text}}} |
Triple curly braces are for nowiki which is optionally monospace in Creole (the choice of the implementor). Future Creole additions may introduce double hash marks (##) for monospace. | |
Markdown | **bold text** or |
*italic text* or |
Non-monospace text
|
Markdown doesn't use bold and italic tags, but rather em (typically italic) and strong (typically bold) tags.Monospace text is created by indenting that line 4 spaces or one tab character, or enclosing text in backticks: |
|
o7aCode | '''bold text''' |
''italic text'' |
°°°
|
o7aCode uses em (typically italic) and strong (typically bold) tags.All attributes of all markups can be filled in. |
|
POD | B<bold text> |
I<italic text> |
C<monospace text> |
Indented text is also shown as monospaced code. | |
reStructuredText | **bold text** |
*italic text* |
``monospace text`` |
||
Textile | *bold text*
or |
_italic text_
or |
@monospace text@ |
Textile uses em (typically italic) and strong (typically bold) tags
on single symbols, and |
|
Texy! | **bold text** |
*italic text* or
|
`monospace text` |
Texy uses by default em (typically italic) and strong (typically bold) tags. It is possible to configure library to use another tags. |
|
txt2tags | **bold text** |
//italic text// |
``monospace text`` |
||
MediaWiki | '''bold text''' |
''italic text'' |
<code>monospace text</code> |
[edit] Section headers
Language | Format | Notes |
---|---|---|
Almost Free Text | * Level 1 Header
|
Up to 4 levels |
BBCode | Does not support section headers | |
Markdown | # Level 1 Header
|
You can optionally "close" the #-style headers with an equal number of #'s. The #-style headers support up to 6 levels. The = and - style headers support only the two shown. |
o7aCode | = Level 3 Header =
|
The title first level can be set (by default : 3). |
POD | =head1 Level 1 heading
|
|
reStructuredText | Chapter 1 Title
|
Any of the following characters can be used as the "underline": = - ` : ' " ~ ^ _ * + # < > . The same character must be used for the same indentation level and may not be used for a new indentation level. |
Textile | h1. Level 1 Header
|
Up to 6 levels |
Texy! | ### Level 1 Header
|
You can optionally "close" the #-style headers with an equal number of #'s. The #-style headers support up to 6 levels. The underlined style headers support four levels (### *** === ----). Real levels are calculated dynamically. |
txt2tags | = Level 1 Header =
|
Using + characters instead of = characters creates numbered headers (the default being unnumbered). |
MediaWiki | == Level 2 Header ==
|
= is available for level 1 header, but its use is discouraged in Wikipedia (reserved for page title). More = are possible, up to 6. |
[edit] Link Syntax
Language | Syntax | Notes |
---|---|---|
Almost Free Text | [Link text (http://www.example.com)] |
Also has support for targeting references within the same text, not just URLs. |
BBCode | [url]http://www.example.com[/url]
|
Some BBCode implementations can auto-parse URLs as well and convert them to a elements. |
Markdown | [Link text](http://www.example.com "optional title attribute")
or |
Allows for an optional title attribute. |
o7aCode | [http://o7aCode.net/ :: official website of o7aCode :: en]o7aCode[/]
|
All attributes can be filled in (href, title, lang ...). The last example allows to make a link to a wikipedia article. |
POD | L</Internal Link>
|
The core POD standard does not support external links with titles. |
reStructuredText | `Link text <http://www.example.com/>`_ |
Can also be done in a non-embedded format which may be seen as more readable. |
Textile | "Link text (optional title attribute)":http://www.example.com
or |
Allows for an optional title attribute. |
Texy! | "Link text .(optional title)[opt. class or ID]{opt. style}":http://www.example.com
or |
Texy! modifiers allows for an optional title attribute, CSS classes, ID, inline style and HTML element attributes. Example: "Link .(title)[class#id]{color: blue;rel:nofollow}" |
txt2tags | [[Link text www.example.com]] |
|
MediaWiki | [[Internal page]]
|
Wikitext can auto-parse URLs as well and convert them to a elements. |
[edit] Comparison of language features
A lot of this was taken from http://bluebones.net/2005/02/humane-text-formats/
Language | HTML export tool | HTML import tool | Tables | Link titles | class attribute | id attribute | Exportable formats | License |
---|---|---|---|---|---|---|---|---|
Almost Free Text [1] | Yes | No | Yes [2] | No | No | No | HTML, LaTeX, lout, DocBook, RTF | Clarified Artistic License |
BBCode | No | No | No | No | No | No | ? | ? |
Markdown | Yes | Yes | No | Yes | No | No | XHTML | BSD-style & GPL (both) |
Markdown_Extra | Yes | Yes | Yes[3] | Yes | No | No | XHTML | BSD-style & GPL (both) |
o7aCode | Yes | Yes | No | Yes | Yes | Yes | XHTML HTML ... | ? |
POD | Yes | ? | No | Yes | ? | ? | HTML, man, LaTeX, plain text | Artistic License, Perl's license |
reStructuredText | Yes | No | Yes | No | Yes | auto | Latex, XML, PseudoXML, HTML (w3c valid) | Python License |
Textile | Yes | No | Yes | Yes | Yes | Yes | XHTML | Textile License |
Texy! | Yes | Yes | Yes | Yes | Yes | Yes | XHTML or HTML (always valid well formed code) | GNU GPL v2 License |
txt2tags | Yes | ? | Yes | Yes | ? | ? | HTML, XHTML, SGML, LaTeX, Lout, UNIX man, MoinMoin, MagicPoint, PageMaker | GPL |
MediaWiki | Yes | Yes | Yes | Yes | Yes | Yes | ? | GNU GPL |
[edit] References
[edit] See also
[edit] External links
- Interesting notes with many links
- C2's list
- Inhabitants of the authoring ecosphere
- outl's list
- A comparison
|