On Sat, Mar 12, 2016 at 11:33 PM, Dan Allen <[email protected]> wrote: > Britton wrote >> >> > Is asciidoc alive enough to be a good idea to start using now? ive >> > seen it around a lot >> > and it still gets lots of download sorry to hear itsnot developed >> > Lex wrote: >> >> Careful how you say it, the Asciidoc *Python implementation* is in >> maintenance mode, but the new Asciidoctor (http://asciidoctor.org/) >> implementation is roaring ahead. > > > Exactly. > > AsciiDoc is very much alive in the Asciidoctor implementation. Adoption of > AsciiDoc is stronger now than ever before and we are nipping at the heels of > Markdown, reStructuredText/Sphinx, DocBook and even LaTeX. AsciiDoc Python > laid a solid foundation for the AsciiDoc language on which to build. The > implementation, on the other hand, is dated.
Nice I'm trying it. A few things so far: * It seems that asciidoctor gem doesn't end up installing a man page for itself. I don't know much about Ruby maybe it's my setup, I have ruby 1.9.2p0 in $HOME/local and I did the gem install thing from the install section and didn't end up with a man page in $HOME/local/share/man where my $MANPATH points. Asciidoc does manage to get its man page there. Looking around I see asciidoc has one but it's hiding in $HOME/lib/ruby/gems/1.9.1/gems/asciidoctor-1.5.4/man/asciidoctor.1 I like to see the autoconf behavior carried forward when possible at least when it's reasonable as it is here. * I like the default asciidoc style better than the asciidoctor default. I didn't quickly find a way to make * asciidoctor use it. Maybe I can just apply the original asciidoc style sheet I'm not sure. It seems like a look that would be worth keeping around as an option at least. * For some reason, the first line of my document after the header comes out bigger in asciidoctor, but not asciidoc. For example I have this: Ditch Your Debugger =================== :nofooter: // Prevent obnoxious "last modified" footer Here's link:why_debuggers_are_bad.html[why]. This article describes an alternative system to using a debugger. There's also The "Here's why" line comes out bigger than subsequent text in asciidoctor but not asciidoc. Looks like maybe its getting some sort of special magic applied based on it's proximity to the header. I like the asciidoc behavior better because it seems less magical. > Relevant to this audience, we're working on a new section of the Asciidoctor > User Manual that covers migration from AsciiDoc Python. It's mostly minor > changes here and there (some of which are simply a result of technology > moving forward), but even small hints can save a lot of time. Good idea. > I'm aware that for a newcomer, it's not very clear from asciidoc.org that > AsciiDoc has other implementations. Lex and I have discussed on other > threads the need for a new landing page focused on the language itself, not It might be worth doing a quicker alternative and just throwing a line or two at the top of the asciidoc home explaining the situation. > the implementations. Unfortunately, I can't dedicate time to that at the > moment. So it's remains a goal. > > I hope that clears some things up. Yes thanks. Britton -- 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.
