The logic inside Parser is a bit of a mess - it works for the most part but could do with some refactoring

• Unify top level process loop with block process loop
• Split out Parser into Sub Parsers / Block specific parsers
• Move away from parsing with Regular Expressions

I am creating a Azure Function and need generate html from string with asciidoc

I studied the library code and test, but I couldn't find how use the classes

I can see Document.Parse() and AsciiDocVisitor, what is the real class to process the asciidoc ?
Can you write any example code?
My input is a string with the asciidoc and need other string with the html

thanks

asciidoctor comes with a rich test suite. Is it possible to run asciidocnet against those tests, using Iron Ruby?

Tables are currently not supported and will throw a NotImplementedException.

@dmetzgar, I was looking to do this today and see you have implemented this already in a fork at https://github.com/dmetzgar/asciidocnet. Would you be happy to open a PR to pull into here?