Kārlis Gaņģis

> 1. won't work in .NET 2.0 > 2. would make the extension code less pretty. I don't think 1. is an issue - since most people even if they...

The only reason I see to keep the 2.0 version is if someone somewhere wants to use it in an environment like SQL Server 2005 that allows to run managed...

Sorry for the late response. Overall my intention for a while now has been to update the readme to say that this package is deprecated and instead recommend to use...

Yes, I would probably to something like this - create a custom renderer that only renders the markup that you allow. This would render some unsupported things like lists or...

To clarify - you are not looking for plain text output but rather markdown output, preserving all the little details? One problem that I see right away - inline links...

Header texts can be left alone - AST contains information from which format it was parsed. I would avoid converting them between formats. For now reference links seem to be...

I have started work on this in the [md-writer](https://github.com/Knagis/CommonMark.NET/tree/md-writer) branch. Perhaps you could try it out and list the issues you can find. Some I know already: - [ ]...

> header texts I will change this to match the number of characters in the previous line > In ordered and unordered lists, the original indent is not preserved I...

Unfortunately I had no time to work on this so it is still in the state you last reviewed...

Adding inline rules is simple - they should be added to [`InlineMethods.InitializeParsers()`](https://github.com/Knagis/CommonMark.NET/blob/master/CommonMark/Parser/InlineMethods.cs#L17). There is some advanced topics regarding the stack used in prioritizing overlapping inlines (such as emphasis and links)...