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
I observed the following behavior:
Without :data-uri: directive: Paths in subdocuments to images are relative to the location of the main document.
With :data-uri: Paths in subdocuments to images are relative to the location of the subdocument.
I usually use the 2. because my subdocuments are independent projects with separate resources. Unfortunately not all backends implement the 2. correctly yet.
For example the html4 and odt backends do not therefore my projects do not compile with these backends.
The ODT backend is a separate project, please file an issue on its site.
Data-uri is not supported by HTML, only xhtml and html5.
They should all follow type two, but there is a bug(s).
@stuart, documentation says images are relative to the referring document. Data-uri correctly uses {indir}/{imagesdir}/{target} but non data-uri uses {imagesdir}/{target} which makes them relative to the working directory (if {imagesdir} is not absolute), not the document directory. It is therefore wrong if for example the document is an included document from another directory, or asciidoc wasn't run in the document directory.
Documentation doesn't mention absolute being accepted, but I'll bet there are lots of documents that depend on that :( so it isn't just as simple as sticking an {indir={outdir}} on the front for non-datauri I don't think.
Cheers
Lex
The text was updated successfully, but these errors were encountered:
On 10 October 2012 04:34, Jens Getreu jens....@gmail.com wrote:
The ODT backend is a separate project, please file an issue on its site.
Data-uri is not supported by HTML, only xhtml and html5.
They should all follow type two, but there is a bug(s).
@stuart, documentation says images are relative to the referring document. Data-uri correctly uses {indir}/{imagesdir}/{target} but non data-uri uses {imagesdir}/{target} which makes them relative to the working directory (if {imagesdir} is not absolute), not the document directory. It is therefore wrong if for example the document is an included document from another directory, or asciidoc wasn't run in the document directory.
Documentation doesn't mention absolute being accepted, but I'll bet there are lots of documents that depend on that :( so it isn't just as simple as sticking an {indir={outdir}} on the front for non-datauri I don't think.
Cheers
Lex
The text was updated successfully, but these errors were encountered: