# Kramdown 0.11.0 released

**URL:** <https://www.ruby-forum.com/t/kramdown-0-11-0-released/195851>\
**Category:** Ruby\
**Created:** [October 1, 2010, 8:55am UTC](https://www.ruby-forum.com/t/kramdown-0-11-0-released/195851 "2010-10-01T08:55:48Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tlockney](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/5e9695/32.png) [@tlockney](https://www.ruby-forum.com/u/tlockney)\
**Post date:** [October 1, 2010, 8:55am UTC](https://www.ruby-forum.com/t/kramdown-0-11-0-released/195851/1 "2010-10-01T08:55:48Z")

</div>

## About kramdown

kramdown (sic, not Kramdown or KramDown, just kramdown) is a _free_  
GPL-licensed [Ruby](http://www.ruby-lang.org) library for parsing 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].

Homepage for installation instructions and documentation:  
[http://kramdown.rubyforge.org](http://kramdown.rubyforge.org)

## kramdown 0.11.0 released

The biggest change in this release is the implementation of the “lazy  
syntax” which allows one to not use the correct indent or block marker  
and still continue a paragraph, blockquote, … The original Markdown  
syntax allows this and it was requested that kramdown allows this, too.  
However, the main reason for adding this syntax to kramdown is not to  
encourage authors to be lazy but to allow kramdown texts to be  
hard-wrapped by other applications (think, for example, email  
programs). Therefore you shouldn’t make active use of this feature when  
creating a kramdown document!

Another important, though minor, change is that invalid HTML tags and  
extensions are not removed anymore. This is done because of the general  
rule that unrecognized elements are treated as simple text.

**Note** : The “internal” API (which is currently everything except the  
`Kramdown::Document` class) has changed and developers may therefore  
need to update their extensions!

## Changes

- 3 major changes:

- 9 minor changes:

- 9 bug fixes:

- 1 deprecation note: