RubyGems - radiant - Versions diffs - 0.9.1 → 1.0.0.rc1 - Mend

radiant 0.9.1 → 1.0.0.rc1

Potentially problematic release.

This version of radiant might be problematic. Click here for more details.

Files changed (1514) hide show

data/vendor/extensions/markdown_filter/vendor/kramdown/README CHANGED

@@ -21,7 +21,7 @@ kramdown has a basic *Cloth API, so using kramdown is as easy as
 Just clone the git repository as described in doc/installation.page you are good to go. You probably
 want to install `rake` so that you can use the provided rake tasks. Aside from that:
-* The `tidy` binary needs to be installed for the html-to-html tests to work.
+* The `tidy` binary needs to be installed for the automatically derived tests to work.
 * The `latex` binary needs to be installed for the latex-compilation tests to work.

data/vendor/extensions/markdown_filter/vendor/kramdown/Rakefile CHANGED

@@ -236,7 +236,7 @@ EOF
   desc "Upload the website to Rubyforge"
   task :publish_website => ['doc'] do
-    sh "rsync -avc --delete --exclude 'wiki' --exclude 'robots.txt'  htmldoc/ gettalong@rubyforge.org:/var/www/gforge-projects/kramdown/"
+    sh "rsync -avc --delete --exclude 'wiki' --exclude 'js/jsMath' --exclude 'robots.txt'  htmldoc/ gettalong@rubyforge.org:/var/www/gforge-projects/kramdown/"
   end
@@ -306,7 +306,7 @@ if defined? Webgen
         lines = term.desc.split(/\n/)
         first = lines.shift
         rest = lines[0..-2].collect {|l| "  " + l}.join("\n")
-        "`#{term.name}`\n: #{first}\n#{rest}"
+        "`#{term.name}`\n: #{first}\n#{rest}\n\n"
       end.join("\n")
     end

data/vendor/extensions/markdown_filter/vendor/kramdown/VERSION CHANGED

	@@ -1 +1 @@
1	- 0.8.0
1	+ 0.11.0

data/vendor/extensions/markdown_filter/vendor/kramdown/bin/kramdown CHANGED

@@ -34,8 +34,8 @@ OptionParser.new do |opts|
   opts.separator "Command line options:"
   opts.separator ""
-  opts.on("-i", "--input ARG", "Specify the input format: kramdown (default)") {|v| options[:input] = v}
-  opts.on("-o", "--ouput ARG", "Specify the output format: html (default) or latex") {|v| format = v}
+  opts.on("-i", "--input ARG", "Specify the input format: kramdown (default) or html") {|v| options[:input] = v}
+  opts.on("-o", "--ouput ARG", "Specify the output format: html (default), kramdown or latex") {|v| format = v}
   opts.on("-v", "--version", "Show the version of kramdown") do
     puts Kramdown::VERSION
@@ -51,13 +51,14 @@ OptionParser.new do |opts|
   opts.separator ""
   Kramdown::Options.definitions.each do |n, definition|
+    no = n.to_s.tr('_', '-')
     if definition.type == Kramdown::Options::Boolean
-      opts.on("--[no-]#{n}") {|v| options[n] = Kramdown::Options.parse(n, v)}
+      opts.on("--[no-]#{no}") {|v| options[n] = Kramdown::Options.parse(n, v)}
     else
       next if definition.type == Object
       type = definition.type
       type = String if type == Symbol
-      opts.on("--#{n} ARG", type) {|v| options[n] = Kramdown::Options.parse(n, v)}
+      opts.on("--#{no} ARG", type) {|v| options[n] = Kramdown::Options.parse(n, v)}
     end
     definition.desc.split(/\n/).each do |line|

data/vendor/extensions/markdown_filter/vendor/kramdown/data/kramdown/document.html CHANGED

@@ -1,7 +1,16 @@
 <html>
   <head>
-    <title></title>
-    <meta name="generator" content="kramdown <%= Kramdown::VERSION %>" />
+<%
+extend ::Kramdown::Utils::HTML
+title = ''
+h = @doc.tree.children.find {|c| c.type == :header}
+if h
+  collector = lambda {|c| c.children.collect {|cc| cc.type == :text ? escape_html(cc.value, :text) : collector.call(cc)}.join('')}
+  title = collector.call(h)
+end
+%>
+    <title><%= title %></title>
+    <meta name="generator" content="kramdown <%= ::Kramdown::VERSION %>" />
   </head>
   <body>
   <%= @body %>

data/vendor/extensions/markdown_filter/vendor/kramdown/doc/{default.less.css → default.scss.css} RENAMED

@@ -1,5 +1,5 @@
-@text-color: #354146;
-@link-color: #1666A3;
+$text-color: #354146;
+$link-color: #1666A3;
 * {
     padding: 0;
@@ -29,10 +29,11 @@ body, table, code {
     background: #364147;
     background-image: -moz-linear-gradient(top, rgba(54,65,71,1), rgba(81,92,96,1));
     background-image: -webkit-gradient(linear, left top, left bottom, from(rgba(54,65,71,1)), to(rgba(81,92,96,1)));
+    position: relative;
 }
 #header {
-    .with-margin;
+    @extend .with-margin;
     position: relative;
     padding: 0 0 0 30px;
@@ -57,6 +58,11 @@ body, table, code {
     }
 }
+#donation {
+    position: absolute;
+    right: 10px;
+    bottom: 5px;
+}
 /* menu */
 #fullnav {
@@ -66,7 +72,7 @@ body, table, code {
 }
 #nav {
-    .with-margin;
+    @extend .with-margin;
     ul {
         height: 40px;
@@ -120,7 +126,8 @@ body, table, code {
 }
 #intro {
-    .with-margin;
+    @extend .with-margin;
     background: #e6e8e9;
     height: auto;
@@ -133,7 +140,7 @@ body, table, code {
     }
     a {
-        color: @link-color;
+        color: $link-color;
         background-color: inherit;
         text-decoration: underline;
     }
@@ -146,7 +153,8 @@ body, table, code {
 /* content */
 #container {
-    .with-margin;
+    @extend .with-margin;
     position: relative;
     clear: both;
     background-color: #fff;
@@ -154,7 +162,7 @@ body, table, code {
     background-image: -webkit-gradient(linear, 0 0, 0 200, from(#eee), to(#fff));
     a {
-        color: @link-color;
+        color: $link-color;
         background-color: inherit;
         text-decoration: underline;
     }
@@ -462,7 +470,8 @@ body, table, code {
 /* footer */
 #footer {
-    .with-margin;
+    @extend .with-margin;
     clear: both;
     margin-top: 20px;
     padding: 5px 20px 30px;

data/vendor/extensions/markdown_filter/vendor/kramdown/doc/default.template CHANGED

@@ -3,12 +3,12 @@
   <head>
     <meta http-equiv="content-type" content="text/html; charset=utf-8" />
     <meta name="author" content="Thomas Leitner" />
-    <meta name="copyright" content="2009 Thomas Leitner" />
+    <meta name="copyright" content="2009-2010 Thomas Leitner" />
     <meta name="description" content="kramdown is a fast, pure-Ruby Markdown-superset converter" />
     <meta name="keywords" content="ruby, kramdown, markdown, text markup" />
     <link href="{relocatable: default.css}" type="text/css" rel="stylesheet" media="screen,projection" />
     <link href="{relocatable: news.atom}" type="application/atom+xml" rel="alternate" />
-    <script src="{relocatable: js/jsMath/easy/load.js}" type="text/javascript"></script>
+    <script src="http://kramdown.rubyforge.org/js/jsMath/easy/load.js" type="text/javascript"></script>
     <title>{title:} | kramdown</title>
   </head>
   <body>
@@ -16,6 +16,15 @@
       <div id="header">
         <h1 id="logo"><a href="{relocatable: /}" title="Homepage">kramdown <span class='slogan'>fast, pure-Ruby Markdown-superset converter</span></a></h1>
       </div>
+      <div id="donation">
+        <form action="https://www.paypal.com/cgi-bin/webscr" method="post">
+          <input type="hidden" name="cmd" value="_s-xclick" />
+          <input type="hidden" name="encrypted" value="-----BEGIN PKCS7-----MIIHJwYJKoZIhvcNAQcEoIIHGDCCBxQCAQExggEwMIIBLAIBADCBlDCBjjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAkNBMRYwFAYDVQQHEw1Nb3VudGFpbiBWaWV3MRQwEgYDVQQKEwtQYXlQYWwgSW5jLjETMBEGA1UECxQKbGl2ZV9jZXJ0czERMA8GA1UEAxQIbGl2ZV9hcGkxHDAaBgkqhkiG9w0BCQEWDXJlQHBheXBhbC5jb20CAQAwDQYJKoZIhvcNAQEBBQAEgYDA8HEgfduoLW7LANqmfG9shb8sk23qWHt1vJ65J7bcOHFW1Hw/aZV7O2Xf2hRtVmHBQemuFBMVCLFFYn1Tj667ay65xPWrbtNdOcxJ6diwwVcrxMJ/EyS7niUKuTfujgmq5ra9CgNy84WSa0Cw/sWSMrK6XMX9brALPBcKbB003TELMAkGBSsOAwIaBQAwgaQGCSqGSIb3DQEHATAUBggqhkiG9w0DBwQITt+KFiwA4NOAgYBJEwBt4G0KjfWMn428qsUqj7nBGl9dhhOT9FsHPoKHm5lmzadeIhtu7vPwqaH5cZAbE/nZBhkV9/MdgWCt9kMkDLD4Jq+TGLa4RDK+ltxErnPNgr9TYvBOGPAoYTXvA12w+KUewhV1cB/gSdz43oHrBPAyO6x4ZWUhndD2+yqZhKCCA4cwggODMIIC7KADAgECAgEAMA0GCSqGSIb3DQEBBQUAMIGOMQswCQYDVQQGEwJVUzELMAkGA1UECBMCQ0ExFjAUBgNVBAcTDU1vdW50YWluIFZpZXcxFDASBgNVBAoTC1BheVBhbCBJbmMuMRMwEQYDVQQLFApsaXZlX2NlcnRzMREwDwYDVQQDFAhsaXZlX2FwaTEcMBoGCSqGSIb3DQEJARYNcmVAcGF5cGFsLmNvbTAeFw0wNDAyMTMxMDEzMTVaFw0zNTAyMTMxMDEzMTVaMIGOMQswCQYDVQQGEwJVUzELMAkGA1UECBMCQ0ExFjAUBgNVBAcTDU1vdW50YWluIFZpZXcxFDASBgNVBAoTC1BheVBhbCBJbmMuMRMwEQYDVQQLFApsaXZlX2NlcnRzMREwDwYDVQQDFAhsaXZlX2FwaTEcMBoGCSqGSIb3DQEJARYNcmVAcGF5cGFsLmNvbTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAwUdO3fxEzEtcnI7ZKZL412XvZPugoni7i7D7prCe0AtaHTc97CYgm7NsAtJyxNLixmhLV8pyIEaiHXWAh8fPKW+R017+EmXrr9EaquPmsVvTywAAE1PMNOKqo2kl4Gxiz9zZqIajOm1fZGWcGS0f5JQ2kBqNbvbg2/Za+GJ/qwUCAwEAAaOB7jCB6zAdBgNVHQ4EFgQUlp98u8ZvF71ZP1LXChvsENZklGswgbsGA1UdIwSBszCBsIAUlp98u8ZvF71ZP1LXChvsENZklGuhgZSkgZEwgY4xCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJDQTEWMBQGA1UEBxMNTW91bnRhaW4gVmlldzEUMBIGA1UEChMLUGF5UGFsIEluYy4xEzARBgNVBAsUCmxpdmVfY2VydHMxETAPBgNVBAMUCGxpdmVfYXBpMRwwGgYJKoZIhvcNAQkBFg1yZUBwYXlwYWwuY29tggEAMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQEFBQADgYEAgV86VpqAWuXvX6Oro4qJ1tYVIT5DgWpE692Ag422H7yRIr/9j/iKG4Thia/Oflx4TdL+IFJBAyPK9v6zZNZtBgPBynXb048hsP16l2vi0k5Q2JKiPDsEfBhGI+HnxLXEaUWAcVfCsQFvd2A1sxRr67ip5y2wwBelUecP3AjJ+YcxggGaMIIBlgIBATCBlDCBjjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAkNBMRYwFAYDVQQHEw1Nb3VudGFpbiBWaWV3MRQwEgYDVQQKEwtQYXlQYWwgSW5jLjETMBEGA1UECxQKbGl2ZV9jZXJ0czERMA8GA1UEAxQIbGl2ZV9hcGkxHDAaBgkqhkiG9w0BCQEWDXJlQHBheXBhbC5jb20CAQAwCQYFKw4DAhoFAKBdMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEwMDcxOTA2MzUwOVowIwYJKoZIhvcNAQkEMRYEFBdLGCmffPW6PMR/W24T+7ktQe1iMA0GCSqGSIb3DQEBAQUABIGAdn5PO7OJuHq/YpWaWKkJMDNhCqAyRyWpaM4LMQXzyA+ADoKvPnpgHrCdJpvB01L/Wk2apJ59CpB7iFerXh6QRgX85lE6HFl3C+GDRikabulgIn0F/1SMeUuvuRZ8g//Z3xcktOzdchB65K2LyUowAV8rpeWGmt8JFNwOZbeqcmw=-----END PKCS7-----
+" />
+          <input type="image" src="https://www.paypal.com/en_US/i/btn/btn_donate_SM.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!" />
+          <img alt="" border="0" src="https://www.paypal.com/en_US/i/scr/pixel.gif" width="1" height="1" />
+        </form>
+      </div>
     </div>
     <div id="fullnav">
       <div id="nav">

data/vendor/extensions/markdown_filter/vendor/kramdown/doc/documentation.page CHANGED

@@ -10,7 +10,7 @@ HTML. However, due to its modular architecture it is able to support additional
 formats. The following input and output formats are currently supported:
 * Input: [kramdown](parser/kramdown.html) (a superset of Markdown), [html](parser/html.html)
-* Output: [HTML](converter/html.html), [LaTeX](converter/latex.html)
+* Output: [HTML](converter/html.html), [LaTeX](converter/latex.html), [kramdown](converter/kramdown.html)
 ## Usage

data/vendor/extensions/markdown_filter/vendor/kramdown/doc/index.page CHANGED

@@ -8,8 +8,42 @@ sort_info: 1
 If you want to get started with kramdown, have a look at the [installation page](installation.html)
 to see how you can install it on your system. Then look through the
 [documentation](documentation.html) for finding information about how to actually use kramdown and
-what parsers/converters it supports. The [syntax](syntax.html) provides a detailed description of
-the superset of Markdown which kramdown supports.
+its parsers/converters. The [syntax](syntax.html) provides a detailed description of the superset of
+Markdown which kramdown supports.
+{tikz:: path: overview.png
+img_attr: {style: 'background:transparent'}
+libraries: [mindmap, trees, arrows]
+transparent: true
+resolution: 300 100
+opts: |
+  mindmap, concept color=black, text=white,
+  root concept/.append style={font=\Large},
+  level 1 concept/.append style={font=\Large, minimum size=2.6cm},
+  level 2 concept/.append style={font=\Large},
+}
+\node[concept, font=\Large] (lib) {kramdown's internal representation}
+  child[concept color=orange, grow=150, ->] {node[concept] (i-kramdown) {kramdown}}
+  child[concept color=orange, grow=210] {node[concept] (i-html) {HTML}}
+  child[concept color=green!50!black, grow=40] {node[concept] (o-html) {HTML}}
+  child[concept color=green!50!black, grow=0] {node[concept] (o-kramdown) {kramdown}}
+  child[concept color=green!50!black, grow=-45] {
+    node[concept] (o-latex) {\LaTeX}
+    child[grow=0] {
+      node[concept] (o-latex-pdf) {PDF}
+    }
+  }
+  child[concept color=green!50!black, grow=-45] {node[concept] {\LaTeX}}
+;
+\draw [dash pattern=on 0pt off 2pt,line width=5pt,arrows=-angle 60,shorten >=15pt,shorten <=10pt,color=orange]
+   (i-kramdown) edge(lib)
+   (i-html) edge (lib);
+\draw [dash pattern=on 0pt off 2pt,line width=5pt,arrows=-angle 60,shorten >=10pt,shorten <=15pt,color=green!50!black]
+   (lib) edge(o-html)
+   (lib) edge (o-kramdown)
+   (lib) edge (o-latex);
+{tikz}
+{: style="text-align: center"}
 ## Bugs, Forums, Mailing Lists
@@ -38,7 +72,6 @@ Markdown implementations because kramdown borrowed many ideas from existing pack
 [PHP Markdown Extra]: http://michelf.com/projects/php-markdown/extra/
 [Maruku]:             http://maruku.rubyforge.org
-[RedCloth]: http://whytheluckystiff.net/ruby/redcloth/
 [BlueCloth]: http://www.deveiate.org/projects/BlueCloth
@@ -55,7 +88,7 @@ It is probably the fastest pure-Ruby Markdown converter available (June 2010), b
 than [Maruku] and about 9x faster than [BlueFeather].
 <p class="a-center">
-The latest version of kramdown is <b>0.8.0</b> and it was released on <b>2010-06-08</b>.
+The latest version of kramdown is <b>0.11.0</b> and it was released on <b>2010-10-01</b>.
 </p>
 [PHP Markdown Extra]: http://michelf.com/projects/php-markdown/extra/

data/vendor/extensions/markdown_filter/vendor/kramdown/doc/quickref.page CHANGED

@@ -310,7 +310,7 @@ This can contain only *span* level elements.
 ## Block Attributes
-{kdlink: {oid: block-inline-attribute-lists, part: "block IALs"}}
+{kdlink: {oid: block-ials, part: "block IALs"}}
 {kdlink: {oid: attribute-list-definitions, part: "ALDs"}}
 You can assign any attribute to a block level element. Just directly follow the block with a *block
@@ -553,7 +553,7 @@ red</span>.
 ## Inline Attributes
-{kdlink: {oid: span-inline-attribute-lists, part: "span IALs"}}
+{kdlink: {oid: span-ials, part: "span IALs"}}
 As with a block level element you can assign any attribute to a span level elements using a *span
 inline attribute list* (or short: span IAL). A span IAL has the same syntax as a block IAL and must

data/vendor/extensions/markdown_filter/vendor/kramdown/doc/syntax.page CHANGED

@@ -26,8 +26,9 @@ document is converted.
 ## Source Text Formatting
 A kramdown document may be in any encoding, for example ASCII, UTF-8 or ISO-8859-1, and the output
-will have the same encoding as the source. The document consists of two types of elements, block
-level elements and span level elements:
+will have the same encoding as the source.
+The document consists of two types of elements, block level elements and span level elements:
 * Block level elements define the main structure of the content, for example, what part of the text
   should be a paragraph, a list, a blockquote and so on.
@@ -43,6 +44,32 @@ beginning of a kramdown document opens up the default indentation level which be
 column of the text.
+## Line Wrapping
+Some lightweight markup syntax don't work well in environments where lines are hard-wrapped. For
+example, this is the case with many email programs. Therefore kramdown allows content like
+paragraphs or blockquotes to be hard-wrapped, i.e. broken across lines. This is sometimes referred
+to as "lazy syntax" since the indentation or line prefix required for the first line of content is
+not required for the consecutive lines.
+Block level elements that support line wrapping always end when one of the following conditions is
+encountered:
+* a [blank line](#blank-lines), an [EOB marker line](#eob-marker), a [block IAL](#block-ials) or the
+  end of the document (i.e. a [block boundary](#block-boundaries)),
+*  or an [HTML block](#html-blocks).
+Line wrapping is allowed throughout a kramdown document. There is one exception, however:
+[headers](#headers) may not be wrapped across lines. This is not an issue in most situations since
+headers normally fit on one line. If a header text gets too long for one line, use HTML syntax
+instead.
+**Note** that it is **NOT** recommended to use lazy syntax to write a kramdown document. The
+flexibility that the kramdown syntax offers due to the issue of line wrapping hinders readability
+and should therefore not be used.
 ### Usage of Tabs
 kramdown assumes that tab stops are set at multiples of four. This is especially important when
@@ -58,7 +85,7 @@ when converting a kramdown document to HTML one needs to take care of the charac
 depending on the output format.
 This means, for example, that you can just use `<`, `>` and `&` in a kramdown document and need not
-think about when to use their HTML entity counterparts. However, if you *do use* HTML entitys or
+think about when to use their HTML entity counterparts. However, if you *do use* HTML entities or
 HTML tags which use one of the characters, the result will be correct nonetheless!
 Since kramdown also uses some characters to mark-up the text, there needs to be a way to escape
@@ -75,6 +102,7 @@ Following is a list of all the characters (character sequences) that can be esca
     _         underscore
     +         plus
     -         minus
+    =         equal sign
     `         backtick
     ()[]{}    left and right parens/brackets/braces
     #         hash
@@ -88,6 +116,21 @@ Following is a list of all the characters (character sequences) that can be esca
     $         dollar sign
+## Block Boundaries
+Some block level elements have to start and/or end on so called block boundaries, as stated in their
+documentation. There are two cases where block boundaries come into play:
+* If a block level element has to start on a block boundary, it has to be preceded by either a
+  [blank line](#blank-lines), an [EOB marker](#eob-marker), a [block IAL](#block-ials) or it has to
+  be the first element.
+* If a block level element has to end on a block boundary, it has to be followed by either a [blank
+  line](#blank-lines), an [EOB marker](#eob-marker), a [block IAL](#block-ials) or it has to be the
+  last element.
 # Structural Elements
 All structural elements are block level elements and they are used to structure the content. They
@@ -98,30 +141,36 @@ can mark up some text as, for example, a simple paragraph, a quote or as a list
 Any line that just contains white space characters such as spaces and tabs is considered a blank
 line by kramdown. One or more consecutive blank lines are handled as one empty blank line. Blank
-lines are mostly used to visually separate block level elements from each other and in this case
-they don't have semantic meaning. However, there are some cases where blank lines do have a semantic
-meaning:
+lines are used to separate block level elements from each other and in this case they don't have
+semantic meaning. However, there are some cases where blank lines do have a semantic meaning:
-* When used in paragraphs -- see the [paragraphs section](#paragraphs)
 * When used in headers -- see the [headers section](#headers)
+* When used in code blocks -- see the [code blocks section](#code-blocks)
 * When used in lists -- see the [lists section](#lists)
+* When used in math blocks -- see the [math blocks section](#math-blocks)
+* When used for elements that have to start/end on [block boundaries](#block-boundaries)
 ## Paragraphs
 Paragraphs are the most used block level elements. One or more consecutive lines of text are
-interpreted as one paragraph. Every line of a paragraph may be indented up to three spaces. You can
-separate two consecutive paragraphs from each other by using one or more blank lines. Notice that a
-line break in the source does not mean a line break in the output! If you want to have an explicit
-line break (i.e. a `<br />` tag) you need to end a line with two or more spaces or two backslashes!
-Note, however, that a line break on the last text line of a paragraph is not possible and will be
-ignored. Leading and trailing spaces will be stripped from the paragraph text.
+interpreted as one paragraph. The first line of a paragraph may be indented up to three spaces, the
+other lines can have any amount of indentation because paragraphs support [line
+wrapping](#line-wrapping). In addition to the rules outlined in the section about line wrapping, a
+paragraph ends when a [definition list line](#definition-lists) is encountered.
+You can separate two consecutive paragraphs from each other by using one or more blank lines. Notice
+that a line break in the source does not mean a line break in the output (due to the [lazy
+syntax](#line-wrapping))!. If you want to have an explicit line break (i.e. a `<br />` tag) you need
+to end a line with two or more spaces or two backslashes! Note, however, that a line break on the
+last text line of a paragraph is not possible and will be ignored. Leading and trailing spaces will
+be stripped from the paragraph text.
 The following gives you an example of how paragraphs look like:
     This para line starts at the first column. However,
-       the lines can be indented up to three spaces.
-    The para continues here.
+          the following lines can be indented any number of spaces/tabs.
+       The para continues here.
       This is another paragraph, not connected to the above one. But
     with a hard line break. \\
@@ -136,12 +185,12 @@ single document.
 ### Setext Style
-Setext style headers are specified by a [blank line](#blank-lines) (except at the beginning of a
-document), followed by a line of text (the header text) and a line with only equal signs (for a
-first level header) or dashes (for a second level header). The header text may be indented up to
-three spaces but any leading or trailing spaces are stripped from the header text. The amount of
-equal signs or dashes is not significant, just one is enough but more may look better. The equal
-signs or dashes have to begin at the first column. For example:
+Setext style headers have to start on a [block boundary](#block-boundaries) with a line of text (the
+header text) and a line with only equal signs (for a first level header) or dashes (for a second
+level header). The header text may be indented up to three spaces but any leading or trailing spaces
+are stripped from the header text. The amount of equal signs or dashes is not significant, just one
+is enough but more may look better. The equal signs or dashes have to begin at the first column. For
+example:
     First level header
     ==================
@@ -152,7 +201,8 @@ signs or dashes have to begin at the first column. For example:
        Other first level header
     =
-As mentioned you need to insert a blank line before (but not necessarily after) a Setext header:
+Since Setext headers start on block boundaries, this means in most situations that they have to be
+preceded by a blank line. However, blank lines are not necessary after a Setext header:
     This is a normal
     paragraph.
@@ -167,7 +217,7 @@ As mentioned you need to insert a blank line before (but not necessarily after)
     ------------
 However, it is generally a good idea to also use a blank line after a Setext header because it looks
-more appropriate.
+more appropriate and eases reading of the document.
 > The original Markdown syntax allows one to omit the blank line before a Setext header. However,
 > this leads to ambiguities and makes reading the document harder than necessary. Therefore it is
@@ -186,13 +236,12 @@ the case. The general rule is that Setext headers are processed before horizonta
 ### atx Style
-atx style headers are specified by a [blank line](#blank-lines) (except at the beginning of a
-document), followed by a line with one or more hash characters and then the header text. No spaces
-are allowed before the hash characters. The number of hash characters specifies the heading level:
-one hash character gives you a first level heading, two a second level heading and so on until the
-maximum of six hash characters for a sixth level heading. You may optionally use any number of
-hashes at the end of the line to close the header. Any leading or trailing spaces are stripped from
-the header text. For example:
+atx style headers have to start on a [block boundary](#block-boundaries) with a line that contains
+one or more hash characters and then the header text. No spaces are allowed before the hash
+characters. The number of hash characters specifies the heading level: one hash character gives you
+a first level heading, two a second level heading and so on until the maximum of six hash characters
+for a sixth level heading. You may optionally use any number of hashes at the end of the line to
+close the header. Any leading or trailing spaces are stripped from the header text. For example:
     # First level header
@@ -226,20 +275,25 @@ trailing hashes. For example:
 ## Blockquotes
 A blockquote is started using the `>` marker followed by an optional space and the content of the
-blockquote. The marker itself may be indented up to three spaces. All following lines that are also
-started with the blockquote marker belong to the blockquote. The contents of a blockquote are block
-level elements. This means that if you are just using text as content that it will be wrapped in a
-paragraph. For example, the following gives you one blockquote with two paragraphs in it:
+blockquote. The marker itself may be indented up to three spaces. All following lines, whether they
+are started with the blockquote marker or just contain text, belong to the blockquote because
+blockquotes support [line wrapping](#line-wrapping).
+The contents of a blockquote are block level elements. This means that if you are just using text as
+content that it will be wrapped in a paragraph. For example, the following gives you one blockquote
+with two paragraphs in it:
     > This is a blockquote.
-    >on multiple lines.
+    >     on multiple lines
+    that may be lazy.
     >
     > This is the second paragraph.
 Since the contents of a blockquote are block level elements, you can nest blockquotes and use other
-block level elements:
+block level elements (this is also the reason why blockquotes need to support line wrapping):
     > This is a paragraph.
+    >
     > > A nested blockquote.
     >
     > ## Headers work
@@ -256,17 +310,16 @@ will have to be indented with five spaces or one space and one tab, like this:
     >
     >     ruby -e 'puts :works'
-> The original Markdown syntax allowed "lazy" blockquotes, i.e. blockquotes where only the first line
-> needs a blockquote marker. This is disallowed in kramdown, you always need to use a blockquote
-> marker! The rational behind this is that most email programs and good text editors put the `>`
-> maker automatically before every quoted line and that things like the following work like
-> expected:
->
->     > > This is some quoted text.
->     > > Spanning multiple lines.
->     > This is the answer to the quoted text above.
->     This is just a normal paragraph, with the answer to the above.
-{: .markdown-difference}
+[Line wrapping](#line-wrapping) allows one to be lazy but hinders readability and should therefore
+be avoided, especially with blockquotes. Here is an example of using blockquotes with line wrapping:
+    > This is a paragraph inside
+    a blockquote.
+    >
+    > > This is a nested paragraph
+    that continues here
+    > and here
+    > > and here
 ## Code Blocks
@@ -274,12 +327,19 @@ will have to be indented with five spaces or one space and one tab, like this:
 Code blocks can be used to represent verbatim text like markup, HTML or a program fragment because
 no syntax is parsed within a code block.
-### Standard Code Block
+### Standard Code Blocks
 A code block can be started by using four spaces or one tab and then the text of the code block. All
-following lines that adhere to this syntax belong to the same code block. The indentation (four
-spaces or one tab) is stripped from the text. Note that blank lines don't separate consecutive code
-blocks:
+following lines containing text, whether they adhere to this syntax or not, belong to the code block
+because code blocks support [line wrapping](#line-wrapping)). A wrapped code line is automatically
+appended to the preceding code line by substituting the line break with a space character. The
+indentation (four spaces or one tab) is stripped from each line of the code block.
+> The original Markdown syntax does not allow line wrapping in code blocks.
+{: .markdown-difference}
+Note that consecutive code blocks that are only separate by [blank lines](#blank-lines) are merged
+together into one code block:
         Here comes some code
@@ -292,7 +352,7 @@ marker](#eob-marker) to separate the two:
     ^
         This one is separate.
-### Fenced Code Block
+### Fenced Code Blocks
 > This alternative syntax is not part of the original Markdown syntax. The idea and syntax comes
 > from the [PHP Markdown Extra] package.
@@ -358,22 +418,36 @@ The following gives you an unordered list and an ordered list:
 The first list marker in a list may be indented up to three spaces. The column number of the first
 non-space character which appears after the list item marker on the same line specifies the
 indentation that has to be used for the following lines of content of the list item. If there is no
-such character, the indentation that needs to be used is four spaces or one tab. If a line does not
-have the needed amount of indentation, it is not treated as list item content. The indentation is
-stripped from the content and the content (note that the content naturally also contains the content
-of the line with the item marker) is processed as text containing block level elements. All other
-list markers in the list may be indented up to three spaces or the number of spaces used for the
-indentation of the last list item minus one, whichever number is smaller. For example:
+such character, the indentation that needs to be used is four spaces or one tab. Indented lines may
+be followed by lines containg text with any amount of indentation due to [line
+wrapping](#line-wrapping). Note, however, that in addition to the rules outlined in the section
+about line wrapping, a list item also ends when a line with another list item marker is encountered
+-- see the next paragraph.
+The indentation is stripped from the content and the content (note that the content naturally also
+contains the content of the line with the item marker) is processed as text containing block level
+elements. All other list markers in the list may be indented up to three spaces or the number of
+spaces used for the indentation of the last list item minus one, whichever number is smaller. For
+example:
     * This is the first line. Since the first non-space characters appears in column 3, all other
-      lines have to be indented 2 spaces so that the first characters align. This tells kramdown
-      that the lines belong to the list item.
+      indented lines have to be indented 2 spaces.
+    However, one could be lazy and not indent a line but this is not recommened.
     *       This is the another item of the list. It uses a different number of spaces for
-            indentation which is okay but should generally be avoided.
-       * The list item marker is indented 3 spaces which is allowed but should also be avoided.
+       indentation which is okay but should generally be avoided.
+       * The list item marker is indented 3 spaces which is allowed but should also be avoided and
+         starts the third list item. Note that the lazy line in the second list item may make you
+         believe that this is a sub-list which it isn't! So avoid being lazy!
 So, while the above is possible and creates one list with three items, it is not advised to use
-different (marker and list content) indents for same level list items!
+different (marker and list content) indents for same level list items as well as lazy indentation!
+It is much better to write such a list in the following way:
+    * This is the first list item bla blabla blabla blabla blabla blabla blabla blabla blabla blabla
+      blabla blabla blabla blabla blabla blabla blabla blabla blabla blabla blabla blabla blabla
+      blabla blabla blabla bla
+    * This is the another item of the list. bla blabla blabla blabla blabla blabla blabla blabla
+      blabla blabla blabla blabla blabla blabla blabla blabla blabla blabla blabla blabla bla
 > The original Markdown syntax also allows you to indent the marker, however, the behaviour of what
 > happens with the list items is not clearly specified and may surprise you.
@@ -388,9 +462,9 @@ example:
     *   Using a tab to indent this line, the tab only counts as three spaces and therefore the
         overall indentation is four spaces.
-       1.   The tab after the marker counts here as two spaces. Since the indentation of the marker
-            is three spaces and the marker itself takes two characters, the overall indentation
-            needed for the following lines is eight spaces or two tabs.
+       1.   The tab after the marker counts here as three spaces. Since the indentation of the
+            marker is three spaces and the marker itself takes two characters, the overall
+            indentation needed for the following lines is eight spaces or two tabs.
 It is clear that you might get unexpected results if you mix tabs and spaces or if you don't have
 the tab stops set to multiples of four in your editor! Therefore this should be avoided!
@@ -443,6 +517,7 @@ Since the content of a list item can contain block level elements, you can do th
         A second paragraph
         * nested list
         > blockquote
     *   Second item
@@ -469,17 +544,6 @@ Note that the list marker needs to be followed with at least one space or tab! O
 not recognized as the start of a list item but interpreted as a paragraph containing the list
 marker.
-> The original Markdown syntax allows you to be lazy when you just use text for a list item. So the
-> following is possible with Markdown:
->
->     * First list item
->     continued here
->     *   Second list item
->       continued here.
->
-> This kind of syntax is disallowed in kramdown.
-{: .markdown-difference}
 If you want to have one list directly after another one (both with the same list type, i.e. ordered
 or unordered), you need to use an EOB marker to separate the two:
@@ -487,16 +551,9 @@ or unordered), you need to use an EOB marker to separate the two:
     ^
     * List two
-It is possible that a line gets parsed as ordered or unordered list although it shouldn't. This
-would be the case in the following example:
-    I have read the book
-    1984. It was great
-    - others say that, too!
-Therefore you have to insert a blank line after a paragraph if you want to follow the paragraph with
-a list. The only exception to this rule is when you want to create a compact nested list, i.e. a
-list where the text is not wrapped in paragraphs:
+Since paragraphs support [line wrapping](#line-wrapping), it would usually not be possible to create
+compact nested list, i.e. a list where the text is not wrapped in paragraphs because there is no
+blank line but a sub list after it:
     *   This is just text.
         * this is a sub list item
@@ -505,9 +562,11 @@ list where the text is not wrapped in paragraphs:
         spanning two lines
       * this is a nested list item.
-Another way to remedy the problem with the list item marker appearing in plain text is by escaping
-the period in an ordered list or the list item marker in an unordered list (this is especially
-useful when the paragraph starts with something looking like a list item marker):
+However, this is an often used syntax and is therefore support by kramdown.
+If you want to start a paragraph with something that looks like a list item marker, you need to
+escape it. This is done by escaping the period in an ordered list or the list item marker in an
+unordered list:
     1984\. It was great
     \- others say that, too!
@@ -530,8 +589,9 @@ after the list item marker:
 Definition lists allow you to assign one or more definitions to one or more terms.
 A definition list is started when a normal paragraph is followed by a line with a definition marker
-(a colon which may be optionally indented up to three spaces), then at least one tab or one space
-and then the first part of the definition. The line with the definition marker may optionally be
+(a colon which may be optionally indented up to three spaces), then at least one tab or one space,
+optionally followed by an [IAL](#inline-attribute-lists) that should be applied to the list item and
+then the first part of the definition. The line with the definition marker may optionally be
 separated from the preceding paragraph by a blank line. The leading tabs or spaces are stripped away
 from this first line of the definition to allow for a nice alignment with the following definition
 content. Each line of the preceding paragraph is taken to be a term and the lines separately parsed
@@ -547,26 +607,29 @@ The following is a simple definition list:
 The column number of the first non-space character which appears after a definition marker on the
 same line specifies the indentation that has to be used for the following lines of the definition.
-If there is no such character, the indentation that needs to be used is four spaces or one tab. If
-one of the following lines does not have the needed amount of indentation, it is not treated as part
-of the definition. The indentation is stripped from the definition and it (note that the definition
-naturally also contains the content of the line with the definition marker) is processed as text
-containing block level elements. If there is more than one definition, all other definition markers
-for the term may be indented up to three spaces or the number of spaces used for the indentation of
-the last definition minus one, whichever number is smaller. For example:
+If there is no such character, the indentation that needs to be used is four spaces or one tab.
+Indented lines may be followed by lines containg text with any amount of indentation due to [line
+wrapping](#line-wrapping). Note, however, that in addition to the rules outlined in the section
+about line wrapping, a list item also ends when a line with another definition marker is encountered.
+The indentation is stripped from the definition and it (note that the definition naturally also
+contains the content of the line with the definition marker) is processed as text containing block
+level elements. If there is more than one definition, all other definition markers for the term may
+be indented up to three spaces or the number of spaces used for the indentation of the last
+definition minus one, whichever number is smaller. For example:
     definition term 1
     definition term 2
     : This is the first line. Since the first non-space characters appears in column 3, all other
-      lines have to be indented 2 spaces so that they first characters align. This tells kramdown
-      that the lines belong to the definition.
+    lines have to be indented 2 spaces (or lazy syntax may be used after an indented line). This
+      tells kramdown that the lines belong to the definition.
     :       This is the another definition for the same term. It uses a different number of spaces
             for indentation which is okay but should generally be avoided.
        : The definition marker is indented 3 spaces which is allowed but should also be avoided.
 So, while the above is possible and creates a definition list with two terms and three definitions
 for them, it is not advised to use different (definition marker and definition) indents in the same
-definition list!
+definition list as well as lazy indentation!
 The definition for a term is made up of text and/or block level elements. If a definition is *not*
 preceded by a blank line, the first part of the definition will just be text if it would be a
@@ -594,13 +657,19 @@ Sometimes one wants to include simple tabular data in a kramdown document for wh
 full-blown HTML table is just too much. kramdown supports this with a simple syntax for ASCII
 tables.
-There are three different text line types that can be used in a table:
+Tables can be created with or without a leading pipe character: If the first line of a table
+contains a pipe character at the start of the line (optionally indented up to three spaces), then
+all leading pipe characters (i.e. pipe characters that are only preceded by whitespace) are ignored
+on all table lines. Otherwise they are not ignored and count when dividing a table line into table
+cells.
+There are four different line types that can be used in a table:
 * *Table rows* define the content of a table.
-  A table row is started with a pipe character, optionally indented up to three spaces, and then the
-  text of the first table cell. Subsequent table cells consist of a pipe character followed by the
-  cell text. One may optionally use a pipe character at the the end of a table row line.
+  A table row is any line that contains at least one pipe character and is not identified as any
+  other type of table line! The table row is divided into indivdual table cells by pipe characters.
+  An optional trailing pipe character is ignored.
   Header rows, footer rows and normal rows are all done using these table rows. Table cells can only
   contain a single line of text, no multiline text is supported. The text of a table cell is parsed
@@ -612,13 +681,14 @@ There are three different text line types that can be used in a table:
       | First cell|Second cell|Third cell
       | First | Second | Third |
+      First | Second | | Fourth |
 * *Separator lines* are used to split the table body into multiple body parts.
-  A separator line is started with a pipe or plus character, optionally indented up to three spaces,
-  followed by an optional space, an optional colon, a dash and then any number and combination of
-  pipes, dashes, pluses, colons and spaces. The pipe and plus characters can be used to visually
-  separate columns although this is not needed. Multiple separator lines after another are treated
-  as one separator line.
+  A separator line is any line that contains only pipes, dashes, pluses, colons and spaces and which
+  contains at least one dash and one pipe character. The pipe and plus characters can be used to
+  visually separate columns although this is not needed. Multiple separator lines after another are
+  treated as one separator line.
   Here are some example separator lines:
@@ -627,6 +697,7 @@ There are three different text line types that can be used in a table:
       |---------|
       |-
       | :-----: |
+      -|-
 * The first separator line after at least one table row is treated specially, namely as *header
   separator line*. It is used to demarcate header rows from normal table rows and/or to set column
@@ -647,6 +718,7 @@ There are three different text line types that can be used in a table:
       |---+---+---|
       + :-: |:------| ---:|
       | :-: :- -: -
+      :-: | :-
 * A *footer separator line* is used to demarcate footer rows from normal table rows. All table rows
   below the footer separator line are considered to be footer rows.
@@ -676,12 +748,20 @@ Given the above components, a table is specified by
 * optionally followed by a footer separator line and zero, one or more table rows and
 * an optional trailing separator line.
+Also note
+* that the first line of a table must not have more than three spaces of indentation before the
+  first none space character,
+* that each line of a table needs to have at least one not escaped pipe character so that kramdown
+  recognizes it as a line belonging to the table and
+* that tables have to start and end on [block boundaries](#block-boundaries)!
 > The table syntax differs from the one used in [PHP Markdown Extra] as follows:
 >
-> * kramdown tables have to begin with a pipe character, this is optional in [PHP Markdown Extra].
 > * kramdown tables do not need to have a table header.
 > * kramdown tables can be structured using separator lines.
 > * kramdown tables can contain a table footer.
+> * kramdown tables need to be separted from other block level elements.
 {: .markdown-difference}
 Here is an example for a kramdown table with a table header row, two table bodies and a table footer
@@ -740,11 +820,12 @@ three spaces. The following examples show different possibilities to create a ho
 kramdown has built-in support for block and span level mathematics written in LaTeX.
-A math block is started using two dollar signs, optionally indented up to three spaces. The math
-block continues until the next two dollar signs (which may be on the same line or on one of the next
-lines) that appear at the end of a line, i.e. they may only be followed by whitespace characters.
-The content of a math block has to be valid LaTeX math. It is always wrapped inside a
-`\begin{displaymath}...\end{displaymath}` enviroment except if it begins with a `\begin` statement.
+A math block needs to start and end on [block boundaries](#block-boundaries). It is started using
+two dollar signs, optionally indented up to three spaces. The math block continues until the next
+two dollar signs (which may be on the same line or on one of the next lines) that appear at the end
+of a line, i.e. they may only be followed by whitespace characters. The content of a math block has
+to be valid LaTeX math. It is always wrapped inside a `\begin{displaymath}...\end{displaymath}`
+enviroment except if it begins with a `\begin` statement.
 The following kramdown fragment
@@ -867,7 +948,7 @@ Parse as raw HTML block
 Parse as block level elements
 :
-        applet button blockquote colgroup dd div dl fieldset form iframe li
+        applet button blockquote body colgroup dd div dl fieldset form iframe li
         map noscript object ol table tbody thead tfoot tr td ul
 Parse as span level elements
@@ -953,8 +1034,8 @@ comments is not processed:
 # Text Markup
-These elements are used inside block level elements to markup text fragments. For example, one can
-easily create links or apply emphasis to certain text parts.
+These elements are all span level elements and used inside block level elements to markup text
+fragments. For example, one can easily create links or apply emphasis to certain text parts.
 Note that empty span level elements are not converted to empty HTML tags but are copied as-is to the
 output.
@@ -984,13 +1065,13 @@ As the wording suggests, inline links provide all information inline in the text
 style links only provide the link text in the text flow and everything else is defined
 elsewhere. This also allows you to reuse link definitions.
-An inline style link can be created by surrounding the link text with square brackets, followed
-immediately by the link URL (and an optional title in single or double quotes preceded by at least
-one space) in normal parentheses. For example:
+An inline style link can be created by surrounding the link text which must contain at least one
+character with square brackets, followed immediately by the link URL (and an optional title in
+single or double quotes preceded by at least one space) in normal parentheses. For example:
     This is [a link](http://rubyforge.org) to a page.
     A [link](../test "local URI") can also have a title.
-    And [spaces](<link with spaces.html>)!
+    And [spaces](link with spaces.html)!
 Notes:
@@ -998,10 +1079,9 @@ Notes:
   However, if you use square brackets within the link text, you have to either properly nest them or
   to escape them. It is not possible to create nested links!
-* The link URL must not contain any spaces and it has to contain properly nested parentheses if no
-  title is specified, or the link URL must be contained in angle brackets (then spaces and
-  incorrectly nested parentheses are allowed). There must not be any spaces before the link URL, and
-  if no title is specified, no spaces are allowed between the link URL and the closing parenthesis.
+* The link URL must not contain single or double quotes and it has to contain properly nested
+  parentheses if no title is specified, or the link URL must be contained in angle brackets
+  (incorrectly nested parentheses are allowed).
 * The link title may not contain its delimiters and may not be empty.
@@ -1029,15 +1109,15 @@ definition looks like this:
     [linkid]: http://www.example.com/ "Optional Title"
-> Link definitions are, despite being described here, block level elements.
+> Link definitions are, despite being described here, non-content block level elements.
 {: .information}
 The link definition has the following structure:
 * The link identifier in square brackets, optionally indented up to three spaces,
 * then a colon and one or more spaces/tabs,
-* then the link URL which must not contain any spaces or a left angle bracket, the link URL which may
-  contain spaces and a right angle bracket,
+* then the link URL which must not contain any single or double quotes and which must contain at
+  least one non-space character, or a left angle bracket, the link URL and a right angle bracket,
 * then optionally the title in single or double quotes, separated from the link URL by one or more
   spaces or on the next line by itself indented any number of spaces/tabs.
@@ -1049,11 +1129,13 @@ The link definition has the following structure:
 Images can be specified via a syntax that is similar to the one used by links. The difference is
 that you have to use an exclamation mark before the first square bracket and that the link text of a
-normal link becomes the alternative text of the image link. As with normal links, image links can be
-written inline or reference style. For example:
+normal link, which may also be the empty string in case of image links, becomes the alternative text
+of the image link. As with normal links, image links can be written inline or reference style. For
+example:
     Here comes a ![smiley](../images/smiley.png)! And here
     ![too](../images/other.png 'Title text'). Or ![here].
+    With empty alt text ![](see.jpg)
 The link definition for images is exactly the same as the link definition for normal links.
@@ -1203,10 +1285,11 @@ A footnote definition is used to define the content of a footnote and has the fo
 * The footnote name in square brackets, optionally indented up to three spaces,
 * then a colon and one or more optional spaces,
 * then the text of the footnote
-* and optionally more text on the following lines which have have to be indented by four spaces or
-  one tab (like with list items).
+* and optionally more text on the following lines which have to follow the syntax for [standard code
+  blocks](#standard-code-blocks) (the leading four spaces/one tab are naturally stripped from the
+  text)
-> Footnote definitions are, despite being described here, block level elements.
+> Footnote definitions are, despite being described here, non-content block level elements.
 {: .information}
 The whole footnote content is treated like block level text and can therefore contain any valid
@@ -1230,8 +1313,8 @@ Here are some example footnote definitions:
 It does not matter where you put a footnote definition in a kramdown document; the content of all
 referenced footnote definitions will be placed at the end of the kramdown document. Not referenced
-foot note definitions are ignored. If more than one footnote definitions have the same footnote
-name, all footnote definitions but the last are ignored.
+footnote definitions are ignored. If more than one footnote definitions have the same footnote name,
+all footnote definitions but the last are ignored.
 ## Abbreviations
@@ -1263,7 +1346,7 @@ Here are some examples:
     *[another language]: It's called Markdown
     *[HTML]: HyperTextMarkupLanguage
-> Abbreviation definitions are, despite being described here, block level elements.
+> Abbreviation definitions are, despite being described here, non-content block level elements.
 {: .information}
@@ -1282,16 +1365,24 @@ kramdown converts the following plain ASCII character into their corresponding t
 * `>>` will become a right guillemet (like this >>) -- an optional leading space will become a
   non-breakable space
-It also replaces normal single `'` and double quotes `"` with "fancy quotes". There *may* be times
-when kramdown falsely replace the quotes. If this is the case, just \'escape\" the quotes and they
-won't be replaced with fancy ones.
+The parser also replaces normal single `'` and double quotes `"` with "fancy quotes". There *may* be
+times when kramdown falsely replace the quotes. If this is the case, just \'escape\" the quotes and
+they won't be replaced with fancy ones.
+# Non-content elements
-# Other Markup
+This section describes the non-content elements that are used in kramdown documents, i.e. elements
+that don't provide content for the document but have other uses such as separating block level
+elements or attaching attributes to elements.
-This section describes markup that is not widely used in kramdown documents but which are sometimes
-needed nonetheless.
+Three non-content block level elements are not described here because they fit better where they
+are:
+* [link definitions](#link-definitions)
+* [footnote definitions](#footnotes)
+* [abbreviation definition](#abbreviations)
 ## End-Of-Block Marker    {#eob-marker}
@@ -1329,10 +1420,9 @@ By using an EOB marker, you can make two lists with one item each:
 This is an implementation of [Maruku]'s feature for adding attributes to block and span level
 elements (the naming is also taken from Maruku). This block level element is used to define
-attributes which can be referenced later. The [Block Inline Attribute
-List](#block-inline-attribute-lists) is used to attach attributes to a block level element and the
-[Span Inline Attribute List](#span-inline-attribute-lists) is used to attach attributes to a span
-level element.
+attributes which can be referenced later. The [Block Inline Attribute List](#block-ials) is used to
+attach attributes to a block level element and the [Span Inline Attribute List](#span-ials) is used
+to attach attributes to a span level element.
 Following are some examples of attribute list definitions (ALDs) and afterwards comes the syntax
 explanation:
@@ -1349,45 +1439,46 @@ An ALD line has the following structure:
   character except a not escaped closing brace),
 * followed by a closing brace and optional spaces until the end of the line.
-The reference name needs to start with a word character or a digit, optionally followed by other word
-characters, digits or dashes.
+The reference name needs to start with a word character or a digit, optionally followed by other
+word characters, digits or dashes.
 There are four different types of attribute definitions which have to be separated by one or more
 spaces:
 references
-:   This must be a valid reference name. It is used to reference an other ALD so that the attributes
-    of the other ALD are also included in this one. The reference name is ignored when collecting the
-    attributes if no attribute definition list with this reference name exists. For example, a
-    simple reference looks like `id`.
+: This must be a valid reference name. It is used to reference an other ALD so that the attributes
+  of the other ALD are also included in this one. The reference name is ignored when collecting the
+  attributes if no attribute definition list with this reference name exists. For example, a simple
+  reference looks like `id`.
 key-value pairs
-:   A key-value pair is defined by a key name, which must follow the rules for reference names, then
-    an equal sign and then the value in single or double quotes. If you need to use the value
-    delimiter (a single or a double quote) inside the value, you need to escape it with a backslash.
-    Key-value pairs can be used to specify arbitrary attributes for block or span level elements. For
-    example, a key-value pair looks like `key1="bef \"quoted\" aft"` or `title='This is a title'`.
+: A key-value pair is defined by a key name, which must follow the rules for reference names, then
+  an equal sign and then the value in single or double quotes. If you need to use the value
+  delimiter (a single or a double quote) inside the value, you need to escape it with a backslash.
+  Key-value pairs can be used to specify arbitrary attributes for block or span level elements. For
+  example, a key-value pair looks like `key1="bef \"quoted\" aft"` or `title='This is a title'`.
 ID name
-:   An ID name is defined by using a hash and then the identifier name which must follow the rules
-    for reference names. This is a short hand for the key-value pair `id="IDNAME"` since this is
-    often used. The ID name specifies the unique ID of a block or span level element. For example,
-    an ID name looks like `#myid`.
+: An ID name is defined by using a hash and then the identifier name which needs to start with a
+  word character or a digit, optionally followed by other word characters, digits, dashes or colons.
+  This is a short hand for the key-value pair `id="IDNAME"` since this is often used. The ID name
+  specifies the unique ID of a block or span level element. For example, an ID name looks like
+  `#myid`.
 class names
-:   A class name is defined by using a dot and then the class name. This is (almost, but not quite)
-    a short hand for the key-value pair `class="class-name"`. Almost because it actually means that
-    the class name should be appended to the current value of the `class` attribute. The following
-    ALDs are all equivalent:
+: A class name is defined by using a dot and then the class name. This is (almost, but not quite) a
+  short hand for the key-value pair `class="class-name"`. Almost because it actually means that the
+  class name should be appended to the current value of the `class` attribute. The following ALDs
+  are all equivalent:
-        {:id: .cls1 .cls2}
-        {:id: class="cls1" .cls2}
-        {:id: class="something" class="cls1" .cls2}
-        {:id: class="cls1 cls2}
+      {:id: .cls1 .cls2}
+      {:id: class="cls1" .cls2}
+      {:id: class="something" class="cls1" .cls2}
+      {:id: class="cls1 cls2}
 As can be seen from the example of the class names, attributes that are defined earlier are
 overwritten by ones with the same name defined later. Also, everything in the attribute definitions
@@ -1401,7 +1492,7 @@ ALDs are processed like they are defined in one ALD.
 These elements are used to attach attributes to another element.
-### Block Inline Attribute Lists
+### Block Inline Attribute Lists   {#block-ials}
 > This syntax feature is not part of the original Markdown syntax. The idea and syntax comes from
 > the [Maruku] package.
@@ -1429,17 +1520,17 @@ Here are some examples for block IALs:
     {:.ruby}
         Some code here
-### Span Inline Attribute Lists
+### Span Inline Attribute Lists      {#span-ials}
 > This syntax feature is not part of the original Markdown syntax. The idea and syntax comes from
 > the [Maruku] package.
 {: .markdown-difference}
-This is a version of the [block inline attribute list](#block-inline-attribute-lists) for span level
-elements. It has the same structure as the block IAL except that leading and trailing spaces are not
-allowed. A span IAL (or two or more span IALs) has to be put directly after the span level element
-to which it should be applied, no additional character is allowed between, otherwise it is ignored
-and only removed from the output.
+This is a version of the [block inline attribute list](#block-ials) for span level elements. It has
+the same structure as the block IAL except that leading and trailing spaces are not allowed. A span
+IAL (or two or more span IALs) has to be put directly after the span level element to which it
+should be applied, no additional character is allowed between, otherwise it is ignored and only
+removed from the output.
 Here are some examples for span IALs:
@@ -1470,7 +1561,7 @@ Here are some examples of how to specify extensions and afterwards is the syntax
 An extension can be specified with or without a body. Therefore there exist a start and an end tag
 for extensions. The start tag has the following structure:
-* an left brace,
+* a left brace,
 * followed by two colons and the extension name,
 * optionally followed by a space and attribute definitions (allowed characters are backslash-escaped
   closing braces or any character except a not escaped closing brace -- same as with ALDs),
@@ -1502,19 +1593,22 @@ The following extensions can be used with kramdown:
 `comment`
-:   Treat the body text as a comment which does not show in the output.
+: Treat the body text as a comment which does not show in the output.
 `nomarkdown`
-:   Don't process the body with kramdown but output it as-is.
+: Don't process the body with kramdown but output it as-is. The attribute `type` specifies which
+  converters should output the body: if the attribute is missing, all converters should output it.
+  Otherwise the attribute value has to be a space separated list of converter names and these
+  converters should output the body.
 `options`
-:   Should be used without a body since the body is ignored. Is used for setting the global options
-    for the kramdown processor (for example, to disable automatic header ID generation). Note that
-    options that are used by the parser are immediately effective whereas all other options are not!
-    This means, for example, that it is not possible to set converter options only for some part of
-    a kramdown document.
+: Should be used without a body since the body is ignored. Is used for setting the global options
+  for the kramdown processor (for example, to disable automatic header ID generation). Note that
+  options that are used by the parser are immediately effective whereas all other options are not!
+  This means, for example, that it is not possible to set converter options only for some part of a
+  kramdown document.