@image and output dir

[Karl Berry]

(More mail from August.)

    I remember than we agreed that @images paths were relative to the 
    result file. So, to have paths right, @image should be searched for in 
    this directory.

    > My inclination is to say that searching the destination directory for
    > any kind of input file, image or otherwise, would just have great

    For input files, indeed it has potential for confusion, but for
    images, it seems to me to be rather logical. The issue with
    images is that they aren't only something that is inputed in a 

For one thing, how do you know what the output directory is?

So if an input document foo.texi contains @image{foo}, then when
foo.texi is processed with makeinfo --html, foo.png/etc. will be
searched for in both foo.texi's directory (fine), anything specified
with -I (fine), and in $(htmldir)? 

Somehow I just can't picture it.  

    manual, they are also part of the final outputed manual (at least 
    in html).

Yes, that's true.  (Images can also be separate files in Info output.)
But I'm not sure that means we should be searching the output directory
at input time.