> > I'll have to find a workaround -- maybe setting 
> > the 'working directory' to the caller one ; hoping that 
> the 
> > filenames will correctly match if the case above is 
> > encountered.
> 
> This would actually be one of the most useful new 
features 
> ever ;)  Especially if it was an option to allow to use 
this 
> 'smart working directory' or use the current 'old' 
method. 

Okay, added in the CVS. All css and js files will now have 
their "children links" established relatively to their 
parent. It should work in most cases, even with this case:

/foo/index.html->css to 'image/image.gif'
/foo/image/image.gif
/bar/deeper/index.html->css to 'image/image.gif'
/bar/deeper/image/image.gif

in fact it should always work, if the relative structure is 
kept.

Available in the upcoming 3.30-alpha