Asciidoctor :: Discussion

Relative paths work differently in asciidoctor-pdf and asciidoctor

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

2 messages Options

kasperni

Relative paths work differently in asciidoctor-pdf and asciidoctor

Hi,

I have some problems with relative paths. And can't figure out whether it is asciidoctor or asciidoctor-pdf that is broken.
I have a project structure looking like that

/adoc/book.adoc
/adoc/chapter1.adoc
/adoc/chapter2.adoc

book.adoc just contains something like this
<<<
include::chapter1.adoc[]
<<<
include::chapter2.adoc[]
<<<

Standing in the root /
> asciidoctor adoc/book.adoc generates a html page with chapter1 and chapter2
> asciidoctor-pdf adoc/book.adoc generates a pdf page that does *not* include chapter 1+2

Standing in /adoc/ and doing
> asciidoctor book.adoc
> asciidoctor-pdf book.adoc
generates (correctly) a html-page/pdf with both chapter 1+2

Is it asciidoctor or asciidoctor-pdf working correctly?

mojavelinux

Re: Relative paths work differently in asciidoctor-pdf and asciidoctor

Administrator

The asciidoctor-pdf command is not performing correctly.

The problem is the implicit header processor extension including in Asciidoctor PDF. I introduced this extension for the Editions application, which assembles NFJS, the Magazine. However, this extension should not be enabled by default because it's changing the behavior of AsciiDoc / Asciidoctor in the general case.

If I disable the extension, then the asciidoctor-pdf command resolves the chapters correctly. I'll fix this for alpha5.

See https://github.com/asciidoctor/asciidoctor-pdf/issues/48

-Dan

On Tue, Sep 9, 2014 at 5:03 AM, kasperni [via Asciidoctor :: Discussion] <[hidden email]> wrote:

Hi,

I have some problems with relative paths. And can't figure out whether it is asciidoctor or asciidoctor-pdf that is broken.
I have a project structure looking like that

/adoc/book.adoc
/adoc/chapter1.adoc
/adoc/chapter2.adoc

book.adoc just contains something like this
<<<
include::chapter1.adoc[]
<<<
include::chapter2.adoc[]
<<<

Standing in the root /
> asciidoctor adoc/book.adoc generates a html page with chapter1 and chapter2
> asciidoctor-pdf adoc/book.adoc generates a pdf page that does *not* include chapter 1+2

Standing in /adoc/ and doing
> asciidoctor book.adoc
> asciidoctor-pdf book.adoc
generates (correctly) a html-page/pdf with both chapter 1+2

Is it asciidoctor or asciidoctor-pdf working correctly?

If you reply to this email, your message will be added to the discussion below:
http://discuss.asciidoctor.org/Relative-paths-work-differently-in-asciidoctor-pdf-and-asciidoctor-tp2159.html

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

Dan Allen | http://google.com/profiles/dan.j.allen