On 7 November 2013 12:45, Stuart Rackham <[email protected]> wrote: > Hi Dan > > I really admire what you et al are doing with Asciidoctor, there's been > a huge amount of work gone into it. Can't have been easy -- AsciiDoc's > current syntax and semantics are the result of over a decade of organic > evolution. > > The Asciidoctor website and the Github Edit/Raw/History integration is > really nice as is the asciidoctor.js project, browser addins and docs. > > Having a baked in testing framework from the get-go is huge and it's the > single biggest difference I've noticed developing Rimu Markup. > > > Cheers, Stuart >
One thing I do notice is that the default title fonts and colours do not match asciidoc's. I notice that on github they do have the same fonts, although not the cooling bluey colour :) Cheers Lex > > > On 07/11/13 12:21, Dan Allen wrote: > > On Wed, Oct 23, 2013 at 8:16 AM, <[email protected] > > <mailto:[email protected]>> wrote: > > > > > > I'll keep my eye out for AsciiDoctor. Basically it is a rewrite of > > the processor (from Python to Ruby)? > > > > > > Correct. GitHub originally started the project because they needed a > > Ruby-based implementation to meet integration, security and performance > > requirements. Without a Ruby implementation, they were strongly > > considering dropping support for AsciiDoc on github.com > > <http://github.com>, which would have been bad news for AsciiDoc. > > > > Now that Asciidoctor has syntax parity with Python AsciiDoc, we're > > interested in evolving and modernizing both the processor and syntax. We > > introduced a mobile-friendly stylesheet that works with original > > AsciiDoc html5 output (which Asciidoctor produces by default). We also > > maintain an asciidoc.conf compatibility file to keep AsciiDoc up to > > speed w/ refinements in Asciidoctor. > > > > I've been very careful to ensure that Asciidoctor can process any > > document written for use with Python AsciiDoc, and as much to the other > > direction as possible. Asciidoctor will be able to run in > > "compatibility" mode for anyone who needs it to be perfectly consistent. > > > > > > I see from the project web page I can download the gem, but I don't > > use Ruby directly very much, only indirectly via utilities like > > homebrew. ``brew search asciidoctor'' and ``brew search doctor'' > > turn up empty tight now. > > > > > > Brew handles installing Ruby, but it doesn't repackage Ruby libraries > > (called RubyGems). I wrote a document for OSX users that explains the > > process. > > > > > http://asciidoctor.org/docs/install-asciidoctor-macosx/#homebrew-procedure > > > > The steps are pretty simple: > > > > brew install ruby > > gem install asciidoctor > > > > ...and possibly an update to the PATH environment variable (refer to the > > guide for details). > > > > Using Ruby is no more difficult than using Python (some may argue > > simpler, opinions vary). What I really like about Ruby is that it runs > > incredibly well on the JVM. Unfortunately, Jython is lagging behind in > > this regard. > > > > -Dan > > > > -- > > Dan Allen | http://google.com/profiles/dan.j.allen > > > > -- > > 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/groups/opt_out. > > -- > 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/groups/opt_out. > -- 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/groups/opt_out.
