Hi,
Is there anyway to know while exporting what is the relative path of the current node?
Let's start with some master org file that includes some other org part from another directory.
This org part references some image with a path relative to its own directory.
I wonder if there is a way to keep track of the actual location of the image file.
I know there is the FILE property, but does it take into account the directory change induced by #include: ?
When exporting to latex, there is always the ability to use graphicspath, but when exporting to html, it could be useful to collect all the files and move them to the publish directory. I'm fiddling with o-blog which does this, but does not address this include issue.
Thanks for any input / idea about this.
--
Fabrice