Open cirosantilli opened 2 years ago
@cirosantilli, thanks for the report. Internally, Asciidoctor ties in a separate TemplateConverter for handling the provided templates; this breaks the asciidoctor-multipage extension. More investigation is needed.
Since --template-dir
isn't working, what is the correct way to change the generated HTML?
Hi @marcj! If --template-dir
is the recommended way to change the generated HTML for Asciidoctor, then it is also the recommended way for asciidoctor-multipage. If you need this issue fixed, please consider contributing by opening a pull request for the necessary changes or sponsoring the project. Thanks!
This issue may require #46 to be done first, because resolving that issue will hopefully provide more control over Asciidoctor generation of the individual output pages.
Gemfile
tmp.adoc
Builds fine with the standard:
Outcome:
out/tmp/tmp.html
andout/tmp/_h2.html
are generated as expected.But if I add
--template-dir template_dir
on the command line to create custom output elements (see https://stackoverflow.com/questions/63917971/how-to-create-custom-html-output-for-an-existing-asciidoctor-asciidoc-macro/63917972#63917972 ):then only
out/tmp/tmp.html
is generated, but notout/tmp/_h2.html
.It does not make a difference it
template_dir
contain anything or not.