I am using Asciidoctor with Gradle and now I want to add PDF generation to the build process. At the moment there is no standard way to convert DOCBOOK generated by Asciidoctor to PDF, instead you can find a bunch of different solutions and I wanted to ask which way the community would prefer:

- Pandoc needs a complex installation, therefore is not suitable for a bootstraping build solution
- I didn't try Sandoc (1), but I think the effort to integrate the solution into a Gradle plugin should't be that high.
- Dan's asciidoctor-fopdf (2): at the moment I am struggeling to adapt the Windows command file and have still some path errors, but the final PDF is already created. The effort to integrate the solution into a Gradle plugin should't be that high.
- Pressgang (3)  provide jdocbook-core, which is the base for the maven-jdocbook-plugin, Gradleware provides a Gradle plugin (4)
- Interessting for me was the way Gradleware took for generating the Gradle documentation PDF: they generate DOCBOOK directly, convert it to HTML and then use Flying Saucer (5) + iText (6) to generate the PDF from HTML (see 7).

What is the prefered way or which way would you recommend?
Kind regards, Christian

PS: I would love to see this forum support Asciidoctor


[1] https://github.com/Hocdoc/sandoc)
[2] https://github.com/mojavelinux/asciidoctor-fopdf
[3] https://github.com/pressgang
[4] https://github.com/gradle/gradle-jdocbook
[5] https://code.google.com/p/flying-saucer/
[6] http://itextpdf.com/
[7] https://github.com/gradle/gradle/tree/master/subprojects/docs

---

If you reply to this email, your message will be added to the discussion below:

http://discuss.asciidoctor.org/PDF-creation-with-Gradle-tp661.html

To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML