On 09/08/2025 22:20, Ihor Radchenko wrote:
Max Nikulin writes:
Perhaps images as objects to export should be introduced in ox. The
challenge is to do it in a backward compatible way (including derived
backends).
When exporting, we will pre-process all the nested links and only the
links that are (a) a sole contents element of the parent link
description; (b) are images.
Frankly speaking, I still do not have solid view on the proposed change.
(b) is inconsistent with generic preview framework where other types of
links (besides images) may define custom overlays. Perhaps :export
function should know whether it called for a nested link, so it should
not generate active link, or it is regular "standalone" link.
Difference between
[[https://orgmode.org][file:image directory/unicorn.svg]]
and
[[https://orgmode.org][<file:image directory/unicorn.svg>]]
may be too subtle (notice a space in the image path).
I was afraid of complications with deactivating link-like text inside
description, but I have realized that it does not differ from similar
text outside of link: either verbatim markup or (unfortunate) zero-width
spaces.
I can not estimate consequences for 3rd party packages that invokes
parser to handle user commands. They must be updated to ignore nested
links. I do not know where handling of special cases is more painful.
