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
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to