Closed polyglot-jones closed 6 months ago
Thanks @polyglot-jones.
For HTML, this assumes that ASCIIDOCTOR is installed on the system path. For EPUB, this assumes that ASCIIDOCTOR-EPUB3 is also installed on the system path. For DOCX, this assumes that PANDOC is also installed on the system path.
These are reasonable assumptions, since the package targets the Asciidoctor family.
I'm merging this PR in the project, although so far I've been avoiding Build features. The problem is that each end user will have his/her own specific needs when it comes to builds — ranging from specific CLI options to implementation specific features (e.g. Ruby vs Java vs JS, etc.).
Being an Asciidoctor Ruby user, I tend to use Rake for all my AsciiDoc projects builds. Furthermore, invoking Asciidoctor via Ruby scripts allows finer control over the process.
Anyhow, having some common presets should be OK (and harmless for those who don't need them), and should allow quick previewing of simple projects.
Fixes #8.
For HTML, this assumes that ASCIIDOCTOR is installed on the system path. For EPUB, this assumes that ASCIIDOCTOR-EPUB3 is also installed on the system path. For DOCX, this assumes that PANDOC is also installed on the system path.
NOTE: There is currently only a WINDOWS implementation for DOCX. (Someone just needs to translate the BAT file into SH scripts for Linux and Mac -- I'll open a pair of new issues for that.)