On Thu, 14 Aug 2014 10:32:20 +0200 Stephan Beal <sgb...@googlemail.com> wrote:
> Correct, but it also means that if you try to view those pages in the > fossil wiki, they will be mangled. That's clear, but originally I was thinking about https://github.com/srackham/asciidoc-fossil-backend which says: "https://github.com/srackham/asciidoc-fossil-backend"; > If you like, as a repayment for saving me weeks of work > writing/debugging another ncurses script binding (by introducing me > to termbox), we can try to get one set up for you with Asciidoc. You're very generous, but let's wait a bit if there is some more interest to integrate/use Asciidoc(tor) with Fossil by using Asciidoctor.js. > If indeed it does support that, then we can plug asciidoc in with little > work. i _know_ somewhere i have an example which dispatches to a different > renderer based on file type, but that might have been in a different source > tree (i can't see to find an example of it in this one). That would be really cool...the more I play with Asciidoc I see it's really capable even to the extent of writing books using it. (I read somewhere that these days it's possible for author writing book in AsciiDoc and submit it to O'Reilly.) So, rich markup + Fossil for keeping it under DVCS sounds as great combo for writers, isn't it? Sincerely, Gour -- You have a right to perform your prescribed duty, but you are not entitled to the fruits of action. Never consider yourself the cause of the results of your activities, and never be attached to not doing your duty. http://www.atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
