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
If the image output directory does not match the value of imagesdir, such as when imagesoutdir is specified, the converter cannot locate the fetched diagram. This particularly affects Asciidoctor PDF, which must read the image in order to embed it.
The current workaround for this situation in Asciidoctor Diagram is to use an absolute path as the image target if the data-uri attribute is set on the document. See:
Since setting the data-uri has other implications, we may decide to settle on a different attribute name.
Since we plan to add support for the imagesdir on the image node in core (see asciidoctor/asciidoctor#3660), one approach is to rely on that enhancement and set the imagesdir attribute on the generated node if it differs from the normal location. That way, the converter doesn't have to do any extra work.
The text was updated successfully, but these errors were encountered:
mojavelinux
changed the title
Fetched diagram cannot be located if image output directory does not match imagesdir
Converter cannot locate fetched diagram if image output directory does not match imagesdir
Jun 4, 2022
@mojavelinux should we anticipate this change and set the imagesdir attribute on the generated node today?
Since we plan to add support for the imagesdir on the image node in core (see asciidoctor/asciidoctor#3660), one approach is to rely on that enhancement and set the imagesdir attribute on the generated node if it differs from the normal location. That way, the converter doesn't have to do any extra work.
So, if imagesoutdir is specified we should set the imagesdir attribute on the generated node? Maybe we should always set the imagesdir on the generated node?
If the image output directory does not match the value of
imagesdir
, such as whenimagesoutdir
is specified, the converter cannot locate the fetched diagram. This particularly affects Asciidoctor PDF, which must read the image in order to embed it.The current workaround for this situation in Asciidoctor Diagram is to use an absolute path as the image target if the
data-uri
attribute is set on the document. See:Since setting the
data-uri
has other implications, we may decide to settle on a different attribute name.Since we plan to add support for the
imagesdir
on the image node in core (see asciidoctor/asciidoctor#3660), one approach is to rely on that enhancement and set theimagesdir
attribute on the generated node if it differs from the normal location. That way, the converter doesn't have to do any extra work.The text was updated successfully, but these errors were encountered: