A different behaviour was detected using snapshot_7446 against v1.70.
There is main file with included part in subfolder. There is other subfolder with the images.
Folder tree:
-files <folder>
--test.xml
-images <folder>
--image01.gif
-main.xml
main.xml:
<book>
<chapter><title>test</title>
<xi:include href="files/test.xml"/>
</chapter>
</book>
test.xml:
...
<informalexample>
<mediaobject>
<imageobject>
<imagedata fileref="../images/image01.gif"/>
</imageobject>
</mediaobject>
</informalexample>
For conversion to HTML Help the XSLTproc is used (with parameter base.dir output/).
Result tree (images folder is moved manually):
-output <folder>
--images <folder>
---image01.gif
--main.html
Path in main.html file is "../images/image01.gif" instead of "images/image01.gif" (as was in 1.70 templates). The same files, the same procedure, only different thing are XSL templates.
Logged In: YES
user_id=582041
Originator: NO
This is probably not a bug. The behaviour is controlled by the keep.relative.image.uris parameter. If the value is non-zero (the default), relative image URIs in the source will be kept in the output. If the value is zero, image URIs are resolved with respect to the base URI. So in order to get the "old" behaviour, set keep.relative.image.uris to zero.
Logged In: YES
user_id=1330552
Originator: YES
Sorry for this item, it is really not a bug. With suggested parameter everything works fine.