tl;dr: if you need to extend AsciiDoc, as of today, use Asciidoctor, nothing else
On Tuesday, May 8, 2018 at 6:22:20 PM UTC-4, Lex Trotman wrote: > > > Note that this implementation of Asciidoc is in Python 2 which will > EOL 1 Jan 2020. If you have a long term need you might want to look > at Asciidoctor or Asciidoc3. I would advise people against looking at AsciiDoc3 now. It just started so it's not mature, it's based on the v2 design which did great for its time but is not easily extensible (look at those config files to get an idea). Also, the maintainer of the new v3 is stubborn with people trying to explain to him how open source software licensing works. Asciidoctor community is where to go for AsciiDoc processing for the time being. As the asciidoctor-reveal.js maintainer, I can say that I would have *never* developed such an extension with Asciidoc2 config files. Also, note that I'm a Python (and Perl) developer, not a Ruby developer. These languages are really similar so it's just a matter of biting the bullet and doing some stackoverflow-style copy and paste programming at the beginning ;) Cheers, -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
