Its been a while since i've been involved in document production and I was never heavily involved in this sort of thing. But I believe that best practice in document authoring was to use XSLT (which uses an XML structure) see https://en.wikipedia.org/wiki/XSLT#:~:text=XSLT%20(Extensible%20Stylesheet%20Language%20Transformations,as%20PDF%2C%20PostScript%20and%20PNG. This is heavily used in the education sector for learning management systems as it allows a single source to be rendered to PDF, HTML etc by passing the XSLT though a different rendering engine. In that environment, a XSLT authoring application is used.
What is not generally known is that Microsoft Word .DOCX is simply a zip file containing an XSLT folder/data structure. Try renaming a .docx file to a .zip file and extract the archive. You might be surprised. I'm sure now is not the time to change authoring environments but it likely explains the convoluted workflow you've found. Asciidoc to me seems to be a very archaic authoring environment. Rod Webster *1300 896 832* +61 435 765 611 VMN® www.vmn.com.au On Sat, 29 Aug 2020 at 10:07, andy pugh <bodge...@gmail.com> wrote: > The path from Asciidoc to PDF is convoluted. It seems to go via XML > and LateX and possibly HTML (But I think that's a parallel path) > > Trying to build a static, working version of the Chinese docs I found > asciidoctor-pdf. > > Good points, it works, and is fast. In fact so fast compared to the > existing toolchain that I assumed it had errored out until I found > that there was a PDF file. > > Bad points. It's a Ruby thing. I think all our platforms have Ruby by > default, but.... > > On the other hand, do we lose the LateX / texlive dependencies? > > -- > > "A motorcycle is a bicycle with a pandemonium attachment and is > designed for the especial use of mechanical geniuses, daredevils and > lunatics." > — George Fitch, Atlanta Constitution Newspaper, 1912 > > > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers > _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
