I have no affinity with Ruby or Python, and have no problem getting the Ruby environment working, including doing a little bit of hacking with Pygments to implement my own lexer for colourising a new language (and Pygments BTW is in Python, so all this is via a Pygments-rb project that bridges Pygments to Ruby).
I had never seen a line of Ruby before this, nor any clue about running the Ruby CLI. But it wasn't hard. I did all this under cygwin on Windows, which is probably the least preferable, and a bit annoying to set up. But now it works just like any Linux or MacOSX environment. Just go with the flow - I have interacted withe Asciidoctor development team, and they are excellent. The language of implementation is the last concern on my mind. W.r.t. Asciidoc and Asciidoctor, I strongly suggest you want to be on the Asciidoctor path, if you are serious about publishing. See my blog post on this <http://wolandscat.net/2015/09/11/goodbye-to-adobe-framemaker-hello-asciidoctor/> . On Sunday, September 13, 2015 at 2:50:20 PM UTC+1, Douglas Nielsen wrote: > > I`m more comfortable in Python and would prefer to use AsciiDoc. However > it seems the last update was 2013 and there is not much support. It seems > AsciiDoctor is more-up-to-date, but is Ruby based. I can get by with > Ruby, but I`d prefer to be in Python environment. > > Is my perception wrong that AsciiDoc is stagnant? > > Thanks. > -- 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 http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
