> ... another reason to choose asciidoctor over asciidoc ... My recommendations are:
1. new projects should always use asciidoctor, it is the developing actively maintained implementation. Asciidoc Python is in static maintenance. And they should use the newer Asciidoctor recommended markups, not the deprecated backward compatible markup. The changes are made with the intention of improving Asciidoc the markup, by ironing out some of the lumps discovered in it and by adding new features. So any new implementations are likely to follow the improved Asciidoctor markup as well. But do use standard markup, don't make customisations, those will lock you into an implementation, and well, if you have customised it, it isn't Asciidoc :) Also Python vs Ruby is a furphy, unless you are intending to program on the implementation it doesn't matter. Both are available for any reasonable development platform. 2. Existing projects which are making significant changes to documents and which use standard Asciidoc should upgrade to the newer recommendations and use Asciidoctor. 3. Any existing project that uses standard Asciidoc and is maintained but doesn't want to or have the effort available to upgrade the documents should use Asciidoctor in compatibility mode, which should involve only changing the build to use the newer tool and its options. 4. That leaves only unmaintained projects and those that have heavily customised Asciidoc left with the Python implementation which is not going to go away soon, but is not proactively upgraded or maintained. Cheers Lex -- 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.
