Re: [bug #35395] bad picture path with --html and --without --no-split

[Karl Berry]

    do not test any longer the presence of some path in --output=FILE 

The problem with not testing for the file is that then there is no way
to know whether it is .png, .jpg, or what.  And we need to know to
construct the final <img> (or whatever).  And we don't want to force
specifying an extension in the @image command, either.

    > with --html, w/o --no-split, and w/o --image-link-prefix :
    > prepend `../'

As I've said before: I recognize that that matches the common practice.
But I still don't see any overriding need to hardwire that convention
into the program (and documentation).  It seems to me that
IMAGE_LINK_PREFIX does the job in the simplest and most complete way.

k