kramdown 0.13.4 → 0.13.5

data/doc/documentation.page

@@ -9,9 +9,12 @@ kramdown is first and foremost a library for converting text written in a supers
 HTML. However, due to its modular architecture it is able to support additional input and output
 formats. The following input and output formats are currently supported:
 
-* Input: [kramdown](parser/kramdown.html) (a superset of Markdown), [Markdown](parser/markdown.html), [html](parser/html.html)
+* Input: [kramdown](parser/kramdown.html) (a superset of Markdown), [Markdown](parser/markdown.html),
+  [HTML](parser/html.html)
 * Output: [HTML](converter/html.html), [LaTeX](converter/latex.html), [kramdown](converter/kramdown.html)
 
+The [kramdown syntax page](syntax.html) describes in detail what is supported and how it differs
+from standard Markdown.
 
 ## Usage
 

data/doc/index.page

@@ -8,8 +8,9 @@ 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
-its parsers/converters. The [syntax page](syntax.html) provides a detailed description of the
-superset of Markdown which kramdown supports.
+its parsers/converters. The [quick reference](quickref.html) provides a overview of the syntax -- if
+you need a more detailed description of the superset of Markdown which kramdown supports the [syntax
+page](syntax.html) is the place to go!
 
 {tikz:: path: overview.png
 img_attr: {style: 'background:transparent'}
@@ -79,20 +80,14 @@ Markdown implementations because kramdown borrowed many ideas from existing pack
 
 --- name:intro
 
-## Welcome to the kramdown site
-
 **kramdown** (sic, not Kramdown or KramDown, just kramdown) is a *free* GPL-licensed
 [Ruby](http://www.ruby-lang.org) library for parsing and converting a superset of Markdown. It is
 completely written in Ruby, supports standard Markdown (with some minor modifications) and various
 extensions that have been made popular by the [PHP Markdown Extra] package and [Maruku].
 
-It is probably the fastest pure-Ruby Markdown converter available (January 2011), being about 4x
+It is probably the fastest pure-Ruby Markdown converter available (February 2012), being about 4x
 faster than [Maruku] and about 5x faster than [BlueFeather].
 
-<p class="a-center">
-The latest version of kramdown is <b>0.13.4</b> and it was released on <b>2011-12-16</b>.
-</p>
-
 [PHP Markdown Extra]: http://michelf.com/projects/php-markdown/extra/
 [Maruku]: http://maruku.rubyforge.org
 [BlueFeather]: http://ruby.morphball.net/bluefeather/index_en.html

data/doc/installation.page

@@ -1,5 +1,5 @@
 ---
-title: Download & Installation
+title: Installation
 in_menu: true
 sort_info: 5
 ---
@@ -8,7 +8,7 @@ sort_info: 5
 ## Dependencies
 
 Since kramdown is written in Ruby, you just need the [Ruby interpreter](http://www.ruby-lang.org),
-version 1.8.5, 1.8.6, 1.8.7 or 1.9.2. There are no other dependencies.
+version 1.8.5, 1.8.6, 1.8.7, 1.9.2 or 1.9.3. There are no other dependencies.
 
 
 ## Compatibility Notes
@@ -16,7 +16,7 @@ version 1.8.5, 1.8.6, 1.8.7 or 1.9.2. There are no other dependencies.
 kramdown should work on any platform which supports Ruby. It has been successfully tested on the
 following platforms:
 
-* Linux with Ruby 1.8.5, 1.8.6, 1.8.7, 1.9.2 and jruby 1.5.0.
+* Linux with Ruby 1.8.5, 1.8.6, 1.8.7, 1.9.2, 1.9.3 and jruby 1.6.0.
 
 See the platform specific installation notes for more information!
 

data/doc/news.page

@@ -1,6 +1,6 @@
 ---
 title: News
-in_menu: true
+in_menu: false
 sort_info: 30
 --- pipeline:tags,blocks,fragments
 

data/doc/quickref.page

@@ -90,7 +90,7 @@ If you set the option `auto_ids` to `false` (for example, by using the `options`
 [Extensions](#extensions)), then the automatic header ID generation is turned off:
 
 {kdexample::}
-{:options auto_ids="false" /}
+{::options auto_ids="false" /}
 
 # A header without an ID
 {kdexample}

data/doc/sidebar.template

@@ -0,0 +1,21 @@
+<h2>News</h2>
+
+<p>The latest version of kramdown is <b>0.13.5</b> and it was released
+on <b>2012-02-19</b>.</p>
+
+<p>More <a href="news.html">news</a>…</p>
+
+<h2>Support kramdown</h2>
+
+<p>If you like kramdown and would like to support it, you are welcome to make a small
+donation (PayPal or Pledgie) -- it will surely be appreciated! Thanks!</p>
+
+<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>
+
+<a href='http://www.pledgie.com/campaigns/16657'><img alt='Click here to lend your support to: kramdown and make a donation at www.pledgie.com !' src='http://www.pledgie.com/campaigns/16657.png?skin_name=chrome' border='0' /></a>

data/doc/syntax.page

@@ -449,24 +449,26 @@ elements. All other list markers in the list may be indented up to three spaces
 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
-      indented lines have to be indented 2 spaces.
-    However, one could be lazy and not indent a line but this is not recommended.
-    *       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 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!
+    * This is the first line. Since the first non-space characters appears in
+      column 3, all other indented lines have to be indented 2 spaces.
+    However, one could be lazy and not indent a line but this is not
+    recommended.
+    *       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 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 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
+    * 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 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
+    * This is the another item of the list. bla blabla blabla blabla blabla
+      blabla blabla blabla blabla blabla blabla blabla blabla blabla blabla
 
 > 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.
@@ -478,12 +480,13 @@ When using tabs for indenting the content of a list item, remember that tab stop
 of four for kramdown. Tabs are correctly converted to spaces for calculating the indentation. For
 example:
 
-    *   Using a tab to indent this line, the tab only counts as three spaces and therefore the
-        overall indentation is four spaces.
+    *   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 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.
+       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!
@@ -556,7 +559,8 @@ problem when you want to have a code block as first element. The solution to thi
 following construct:
 
     * 
-            This is a code block (indentation needs to be 4(1)+4(1) spaces (tabs)).
+            This is a code block (indentation needs to be 4(1)+4(1)
+            spaces (tabs)).
 {: .show-whitespaces .ws-lr}
 
 Note that the list marker needs to be followed with at least one space or tab! Otherwise the line is
@@ -639,12 +643,15 @@ 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 (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.
+    : This is the first line. Since the first non-space characters appears in
+    column 3, all other 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
@@ -655,12 +662,13 @@ preceded by a blank line, the first part of the definition will just be text if
 paragraph otherwise:
 
     definition term
-    : This definition will just be text because it would normally be a paragraph and the there is
-      no preceding blank line.
+    : This definition will just be text because it would normally be a
+      paragraph and the there is no preceding blank line.
 
       > although the definition contains other block-level elements
 
-    : This definition *will* be a paragraph since it is preceded by a blank line.
+    : This definition *will* be a paragraph since it is preceded by a
+      blank line.
 
 The rules about having any block-level element as first element in a list item also apply to a
 definition.
@@ -885,12 +893,23 @@ $$
 $$
 
 Using inline math is also easy: just surround your math content with two dollar signs, like with a
-math block.
+math block. If you don't want to start an inline math statement, just escape the dollar signs and
+they will be treated as simple dollar signs.
 
-If you don't want to start a math block or an inline math statement, just escape the dollar signs
-and they will be treated as simple dollar signs. If you want to start an inline math statement at
-the beginning of a paragraph, just escape the first dollar sign.
+If you have a paragraph that looks like a math block but should actually be a paragraph with just an
+inline math statement, you need to escape the first dollar sign:
 
+    The following is a math block:
+
+    $$ 5 + 5 $$
+
+    But next comes a paragraph with an inline math statement:
+
+    \$$ 5 + 5 $$
+
+If you don't even won't the inline math statement, escape the first two dollar signs:
+
+    \$\$ 5 + 5 $$
 
 ## HTML Blocks
 
@@ -919,9 +938,10 @@ content is parsed:
   raw HTML again. However, if a tag has a `markdown` attribute, this attribute controls parsing of
   this one tag (see below).
 
-  Note that only correct XHTML is supported! This means that you have to use, for example, `<hr />`
-  instead of `<hr>` (although kramdown tries to fix such things if possible). If an invalid closing
-  tag is found, it is ignored.
+  Note that the parser basically supports only correct XHTML! However, there are some exceptions.
+  For example, attributes without values (i.e. boolean attributes) are also supported and elements
+  without content like `<hr />` can be written as `<hr>`. If an invalid closing tag is found, it is
+  ignored.
 
 * Parse as block-level elements: If the HTML/XML tag content should be parsed as text containing
   block-level elements, the remaining text on the line will be parsed by the block-level parser as
@@ -940,6 +960,8 @@ inside a raw HTML block.
 
 Also, if an invalid closing tag is found, it is ignored.
 
+Note that all HTML tag and attribute names are converted to lowercase!
+
 By default, kramdown parses all block HTML tags and all XML tags as raw HTML blocks. However, this
 can be configured with the `parse_block_html`. If this is set to `true`, then syntax parsing in HTML
 blocks is globally enabled. It is also possible to enable/disable syntax parsing on a tag per tag
@@ -1014,7 +1036,8 @@ appears after a start/end tag but on the same line, is processed as if it appear
     which is continued here.
     </div>
 
-    <p markdown="1">This works without problems because it is parsed as span-level elements</p>
+    <p markdown="1">This works without problems because it is parsed as
+    span-level elements</p>
 
     <div markdown="1">The end tag is not found because
     this line is parsed as a paragraph</div>
@@ -1220,7 +1243,8 @@ You can insert one optional space after the starting and before the ending delim
 are not used in the output). For example:
 
     Here is a literal `` ` `` backtick.
-    And here is ``  `some`  `` text (note the two spaces so that one is left in the output!).
+    And here is ``  `some`  `` text (note the two spaces so that one is left
+    in the output!).
 
 A single backtick surrounded by spaces is treated as literal backtick. If you want to force the
 literal meaning of a backtick you can backslash-escape it:
@@ -1510,8 +1534,11 @@ class names
       {: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
-part that does not match one of the above four types is ignored.
+overwritten by ones with the same name defined later.
+
+> Also, everything in the attribute definitions part that does not match one of the above four types
+> is ignored.
+{:.information}
 
 If there is more than one ALD with the same reference name, the attribute definitions of all the
 ALDs are processed like they are defined in one ALD.

data/doc/tests.page

@@ -17,12 +17,14 @@ to verify that the implementation matches the kramdown specification.
 
 If you believe you have found a bug in the implementation, please follow these steps:
 
-* Check the syntax page and see if the behaviour is not intended.
+* Check the [syntax page](syntax.html) and see if the behaviour is not intended.
 
 * If the behaviour is not intended and it seems that kramdown should parse some text in another
-  fashion, please open a bug report and attach two files: one with the text and one with the HTML
+  fashion, please open a [bug report] and attach two files: one with the text and one with the HTML
   conversion you think is correct.
 
+[bug report]: http://rubyforge.org/tracker/?atid=28673&group_id=7403&func=browse
+
 
 # Benchmark
 
@@ -30,7 +32,7 @@ kramdown comes with a small benchmark to test how fast it is in regard to four o
 implementations: Maruku, BlueFeather, BlueCloth and RDiscount. The first two are written using only
 Ruby, the latter two use the C discount library for the actual hard work (which makes them really
 fast but they do not provide additional syntax elements). As one can see below, kramdown is
-currently (November 2010) ~3-4x faster than Maruku, ~4-5x faster than BlueFeather but ~30x slower
+currently (February 2012) ~3-4x faster than Maruku, ~4-5x faster than BlueFeather but ~30x slower
 than BlueCloth and rdiscount:
 
 <pre><code>
@@ -46,7 +48,7 @@ different Ruby interpreters:
 ![ruby 1.8.7p249]({relocatable: img/graph-ruby-1.8.7-249.png})
 ![ruby 1.8.7p302]({relocatable: img/graph-ruby-1.8.7-302.png})
 ![ruby 1.9.2p136]({relocatable: img/graph-ruby-1.9.2p136-136.png})
-![ruby 1.9.3p0]({relocatable: img/graph-ruby-1.9.3p0-0.png})
+![ruby 1.9.3p125]({relocatable: img/graph-ruby-1.9.3p125-125.png})
 
 [Markdown Test Suite]: http://daringfireball.net/projects/downloads/MarkdownTest_1.0.zip
 [MDTest]: http://www.michelf.com/docs/projets/mdtest-1.0.zip

data/lib/kramdown.rb

@@ -1,7 +1,7 @@
 # -*- coding: utf-8 -*-
 #
 #--
-# Copyright (C) 2009-2010 Thomas Leitner <t_leitner@gmx.at>
+# Copyright (C) 2009-2012 Thomas Leitner <t_leitner@gmx.at>
 #
 # This file is part of kramdown.
 #

data/lib/kramdown/compatibility.rb

@@ -1,7 +1,7 @@
 # -*- coding: utf-8 -*-
 #
 #--
-# Copyright (C) 2009-2010 Thomas Leitner <t_leitner@gmx.at>
+# Copyright (C) 2009-2012 Thomas Leitner <t_leitner@gmx.at>
 #
 # This file is part of kramdown.
 #
@@ -23,13 +23,27 @@
 #
 # :stopdoc:
 
-if RUBY_VERSION == '1.8.5'
+if RUBY_VERSION <= '1.8.6'
   require 'rexml/parsers/baseparser'
   module REXML
     module Parsers
       class BaseParser
-        UNAME_STR= "(?:#{NCNAME_STR}:)?#{NCNAME_STR}"
+        UNAME_STR= "(?:#{NCNAME_STR}:)?#{NCNAME_STR}" unless const_defined?(:UNAME_STR)
       end
     end
   end
+
+  if !String.instance_methods.include?("start_with?")
+
+    class String
+      def start_with?(str)
+        self[0, str.length] == str
+      end
+      def end_with?(str)
+        self[-str.length, str.length] == str
+      end
+    end
+
+  end
+
 end

data/lib/kramdown/converter.rb

@@ -1,7 +1,7 @@
 # -*- coding: utf-8 -*-
 #
 #--
-# Copyright (C) 2009-2010 Thomas Leitner <t_leitner@gmx.at>
+# Copyright (C) 2009-2012 Thomas Leitner <t_leitner@gmx.at>
 #
 # This file is part of kramdown.
 #

data/lib/kramdown/converter/base.rb

@@ -1,7 +1,7 @@
 # -*- coding: utf-8 -*-
 #
 #--
-# Copyright (C) 2009-2010 Thomas Leitner <t_leitner@gmx.at>
+# Copyright (C) 2009-2012 Thomas Leitner <t_leitner@gmx.at>
 #
 # This file is part of kramdown.
 #

data/lib/kramdown/converter/html.rb

@@ -1,7 +1,7 @@
 # -*- coding: utf-8 -*-
 #
 #--
-# Copyright (C) 2009-2010 Thomas Leitner <t_leitner@gmx.at>
+# Copyright (C) 2009-2012 Thomas Leitner <t_leitner@gmx.at>
 #
 # This file is part of kramdown.
 #
@@ -315,7 +315,8 @@ module Kramdown
 
       def convert_math(el, indent)
         block = (el.options[:category] == :block)
-        "<script type=\"math/tex#{block ? '; mode=display' : ''}\">#{el.value}</script>#{block ? "\n" : ''}"
+        value = (el.value =~ /<|&/ ? "<![CDATA[#{el.value}]]>" : el.value)
+        "<script type=\"math/tex#{block ? '; mode=display' : ''}\">#{value}</script>#{block ? "\n" : ''}"
       end
 
       def convert_abbreviation(el, indent)

data/lib/kramdown/converter/kramdown.rb

@@ -1,7 +1,7 @@
 # -*- coding: utf-8 -*-
 #
 #--
-# Copyright (C) 2009-2010 Thomas Leitner <t_leitner@gmx.at>
+# Copyright (C) 2009-2012 Thomas Leitner <t_leitner@gmx.at>
 #
 # This file is part of kramdown.
 #
@@ -96,7 +96,13 @@ module Kramdown
         first, second, *rest = inner(el, opts).strip.gsub(/(.{1,#{w}})( +|$\n?)/, "\\1\n").split(/\n/)
         first.gsub!(/^(?:(#|>)|(\d+)\.|([+-]\s))/) { $1 || $3 ? "\\#{$1 || $3}" : "#{$2}\\."} if first
         second.gsub!(/^([=-]+\s*?)$/, "\\\1") if second
-        [first, second, *rest].compact.join("\n") + "\n"
+        res = [first, second, *rest].compact.join("\n") + "\n"
+        if el.children.length == 1 && el.children.first.type == :math
+          res = "\\#{res}"
+        elsif res.start_with?('\$$') && res.end_with?("\\$$\n")
+          res.sub!(/^\\\$\$/, '\$\$')
+        end
+        res
       end
 
 
@@ -112,7 +118,7 @@ module Kramdown
       def convert_header(el, opts)
         res = ''
         res << "#{'#' * el.options[:level]} #{inner(el, opts)}"
-        res << "   {##{el.attr['id']}}" if el.attr['id']
+        res << "   {##{el.attr['id']}}" if el.attr['id'] && !el.attr['id'].strip.empty?
         res << "\n"
       end
 
@@ -351,7 +357,7 @@ module Kramdown
       end
 
       def convert_math(el, opts)
-        (@stack.last.type == :p && opts[:prev].nil? ? "\\" : '') + "$$#{el.value}$$" + (el.options[:category] == :block ? "\n" : '')
+        "$$#{el.value}$$" + (el.options[:category] == :block ? "\n" : '')
       end
 
       def convert_abbreviation(el, opts)
@@ -398,12 +404,12 @@ module Kramdown
       def ial_for_element(el)
         res = el.attr.map do |k,v|
           next if [:img, :a].include?(el.type) && ['href', 'src', 'alt', 'title'].include?(k)
-          next if el.type == :header && k == 'id'
+          next if el.type == :header && k == 'id' && !v.strip.empty?
           if v.nil?
             ''
-          elsif k == 'class'
+          elsif k == 'class' && !v.empty?
             " " + v.split(/\s+/).map {|w| ".#{w}"}.join(" ")
-          elsif k == 'id'
+          elsif k == 'id' && !v.strip.empty?
             " ##{v}"
           else
             " #{k}=\"#{v.to_s}\""