You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The only reason why a forked JVM is spawned to run asciidoctor-epub3 I know is passing path to Kindlegen executable. But, since asciidoctor/asciidoctor-epub3#277 (already available in current asciudoctor-epub3 release that you use), it is possible to pass path through ebook-kindlegen-path document attribute, so it looks like there's no more need to fork.
If you encounter any issues implementing this, feel free to bugreport them to asciidoctor-epub3 project.
The text was updated successfully, but these errors were encountered:
The only reason why a forked JVM is spawned to run asciidoctor-epub3 I know is passing path to Kindlegen executable. But, since asciidoctor/asciidoctor-epub3#277 (already available in current asciudoctor-epub3 release that you use), it is possible to pass path through
ebook-kindlegen-path
document attribute, so it looks like there's no more need to fork.If you encounter any issues implementing this, feel free to bugreport them to asciidoctor-epub3 project.
The text was updated successfully, but these errors were encountered: