On Thu, March 22, 2012 3:58 pm, Gour wrote: > On Thu, 22 Mar 2012 16:15:07 +0100 > Stephan Beal <sgb...@googlemail.com> wrote: > >> AsciiDoc sounds intriguing, though, and i will also be looking for a >> JS implementation of it. > > It is indeed...very capable to write complete books with index, > bibliography, glossary...plus rich semantic. I like it much more than > reST...Markdown is, anyway, not the same league. > > Otoh, I'm not aware of any JS implementation 'cause it's very much tied > to DocBook. Iow, AsciiDoc has very rich markup and it's not, imho, just > question of rendering.
Asciidoc is written in Python, and seems to depend internally on pattern-matching, templates, and naming conventions. The scope of its markup was (as far as I can tell) determined by the need to produce Docbook output, but structurally, Docbook is just another back-end. I can't see it being easy to rewrite in JS though - Perl or Tcl possibly, but that's not much help. Personally I have no problem with saying, this is my documentation source (in Asciidoc markup), from which I might build html or PDF or manpage, but also Fossil-compatible markup so that the same documentation from the same source can also be nicely-formatted embedded documentation. Even though I am normally against checking in built files. I think this is about embedded documentation more than about wiki pages, i.e. the latter are not documentation, just information exchange among developers. Eric -- ms fnd in a lbry _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
