On Wed, 3 Mar 2021 at 08:51, 'Zam' via asciidoc <[email protected]> wrote: > > Nicely put, Dan. Thank you for chipping in. Any ideas about what would be the > best DocBook toolchain to use? And, is a2x still the best toolchain manager? > > I'm now wondering if it is possible, at all, to have a2x installed without > the legacy AsciiDoc processor. I'm betting, however, this is not only > technically unpractical, but outright heresy... What are your thoughts on > this Lex? Please, have mercy on me ;-)
I don't think its separately packaged, so probably it can't be installed by itself using package mechanisms, but AFAIK its a single standalone Python file and so long as you grab the python 3 version https://github.com/asciidoc-py/asciidoc-py/blob/main/asciidoc/a2x.py you shouldn't need anything else (apart from the toolchain of course, but being an ex-latexist you have most of that already). AFAIK it doesn't need "installation" it can just be run "a2x.py argument list" on linux or "python3 a2x.py argument list" on any platform. I don't agree with Dan's assessment of a2x, if it works for you its fine to use, old doesn't mean bad, it hasn't changed much because it hasn't needed to. Or you could use xmlto (but which is a shell script so may not work on non-linux platforms if thats of any importance to you). I'm afraid you probably need to try them and find what works best for you in your particular use-cases. > > I'm thinking of using AsciiDoc (and, most probably, Asciidoctor, giving the > fact that my AsciiDoc.py installation is still at an impasse) for writing my > notes, blog posts, invoices and reports, while still using LaTeX for what it > is best at, i.e., working with---and beautifully typesetting---formulas and > abundant amounts of bibliographical material to be printed out (and possibly > published). Even so, I would like to have the opportunity of working with a > DocBook toolchain from time-to-time, to try out new things. As Dan says, many projects using the docbook toolchain have their own build tools for other things anyway (make, cmake, weird java stuff, whatever), and just integrate whatever docbook tools they need with that. So complex toolchain managers were not high priority for anyone. Basically now that you are getting into personal opinion, it is the sort of question SO would block, and our advice may become less useful unless you happen to align with one of our viewpoints :-). Cheers Lex > > Thank you all for your thoughtful responses. > > Cheers, > > Zam > El martes, 2 de marzo de 2021 a la(s) 03:04:26 UTC-5, [email protected] > escribió: >> >> > Lex wrote: >> > asciidoctor can generate docbook so it can be fed to dblatex and latex in >> > the same way. Or the xslproc/fop chain can be used. >> >> To confirm, I use the later pipeline from time to time, as do several heavy >> Asciidoctor users. I think Apache FOP does an amicable job of generating >> PDFs from DocBook and is actually where some of the inspiration for >> Asciidoctor PDF originated. (Asciidoctor PDF has gone a lot further, but FOP >> still does some things better, like footnotes). I test the dblatex pipeline >> less often because dblatex requires so many packages to be installed. When I >> do need to test it, I tend to resort to Docker so I can keep it contained. >> But I do know that it works. It might be a topic worthy of some >> documentation on the Asciidoctor docs site. >> >> Best Regards, >> >> -Dan >> >> -- >> Dan Allen (he, him, his) | @mojavelinux | https://twitter.com/mojavelinux > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/asciidoc/a375a7cc-4b39-40c4-9372-eac7519fb886n%40googlegroups.com. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/asciidoc/CAKhWKDM%3Dq7X%2B5WFi6Cxm-Cr3ZUPy_iF89wgBE5CbQAQVgCt2mg%40mail.gmail.com.
