Warnings Building Book

[philosopherdog]

running asciidoctor-pdf -v -t -D output \ using-combine-book.adoc generates: asciidoctor: WARNING: coreconcepts.adoc: line 289: no callout found for <1> asciidoctor: WARNING: coreconcepts.adoc: line 290: no callout found for <2> asciidoctor: WARNING: coreconcepts.adoc: line 291: no callout found for <3> asciidoctor: WARNING: coreconcepts.adoc: line 292: no callout found for <4> asciidoctor: WARNING: coreconcepts.adoc: line 294: no callout found for <5> asciidoctor: WARNING: coreconcepts.adoc: line 295: no callout found for <6>

Also, in the installation instructions you are missing: gem install asciidoctor-pdf

I'm using the non-docker way of installing everything on Catalina.

[heckj]

Thanks Steve,

I knew about the warnings, as I was abusing a specific section where I made my own image and wanted to try using the callout format used in the code examples. I was seeing a lot of variation over the early parts of this project (as well as trying a few experiments on extending asciidoc myself) that had me dive for the docker-locked-down version of installation, just to keep things consistent while I concentrated on the content, rather than the rendering

• joe

On Feb 22, 2020, at 7:10 AM, Steve [email protected] wrote: running asciidoctor-pdf -v -t -D output \ using-combine-book.adoc generates: asciidoctor: WARNING: coreconcepts.adoc: line 289: no callout found for <1> asciidoctor: WARNING: coreconcepts.adoc: line 290: no callout found for <2> asciidoctor: WARNING: coreconcepts.adoc: line 291: no callout found for <3> asciidoctor: WARNING: coreconcepts.adoc: line 292: no callout found for <4> asciidoctor: WARNING: coreconcepts.adoc: line 294: no callout found for <5> asciidoctor: WARNING: coreconcepts.adoc: line 295: no callout found for <6>

Also, in the installation instructions you are missing: gem install asciidoctor-pdf

I'm using the non-docker way of installing everything on Catalina.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.