Asciidoctor – A fast, open-source text processor and publishing toolchain

There are so many markup languages and conversion possibilities, just have a look on the to-from option from pandoc. Personally, I prefer reStructuredText, its design feels more consistent in comparison to the ambiguous implementations of the various markdown dialects. In Asciidoc, I do not like that lower lever headings occupy more markers than higher level ones. Visually, === This heading appears more important than == This heading By the way, a good comparison is at http://hyperpolyglot.org/lightweight-markup

AsciiDoc (the format) is currently being developed in an Eclipse Foundation working group (https://projects.eclipse.org/working-group/asciidoc). This working group includes leads from both the Asciidoctor/Ruby and Asciidoc/Python projects. (I'm lurking on the mailing lists but not really part of this effort.) It seems like the goal is to shore up the AsciiDoc standard and prevent further divergence between Python AsciiDoc tools and AsciiDoctor. IMO AsciiDoc's advantage over Markdown, RST, LaTeX and others is its…

I’ve in recent years started to favor reStructuredText over AsciiDoc for three reasons. 1) Docutils’s output in like 95% good, semantic HTML where Asciidoctor has a lot of issues (I would note that non-Docutils is often bad, second-class & reliant on what Markdown outputs for ‘compatibility’ (meaning less features for you)) 2) the features difference between the two I prefer the rST set (such as abbreviations) 3) the spec seems so complicated Pandoc can’t realistically have a reader, just a…