On Sat, Nov 21, 2020 at 05:20:00PM +0000, Gavin Smith wrote: > On Thu, Nov 19, 2020 at 10:11 PM Patrice Dumas <[email protected]> wrote: > > I think that if the path does not starts with . or .. or is an absolute > > path, it would make sense > > 1) to search in include directories (I think that the current directory > > is always in front of of the search path) > > 2) to check if the directories and image file exist in the destination > > directory and if not copy the file > > > > For point 2), there could be a customization variable to prevent the > > copy, that would be off in the default case, but can be turned on for > > the users who want backward compatibility or do something else by > > themselves, for instance use links. > > That sounds okay, as searching include directories matches what > happens with TeX. When you say "current directory" this should mean > the directory containing the Texinfo file, not the working directory > from which texi2any is run. (What to do when a file in a subdirectory > is @include'd and then references an image, I don't know.)
I think that it is the current directory, not the directory containing the Texinfo file, but I do not think that it matters much. I think that the point is to copy the image file from where it is found to the destination directory. -- Pat
