> I don't know if using the near flag would fix the
> issue or not. I think I tried using the near flag on
> a site one time to see if it would grab the not
> mirrored images, but I don't remember the results. I
> have my own reasons for preferring not to use the
> near flag anyway.

It's very simple to test the issue, just make a new winhttrack project with
only <http://1.www.s81c.com/common/v17/css/www_1.css> as "web addresses". Set
the "near flag" or not, reset the options to default or use your usual ones at
your wish, it would in fact be nice to know there are settings that make it
work; I strongly believe you will always meet the problem though.

That css is very dense, you can easily see the problem by using a formatter
such as www.codebeautifier.com with the least optimizations (for
www.codebeautifier.com Preserve CSS: checked, Compression: low , Regroup
selectors: do not change anything, Optimise shorthands: don't optimise and all
other check boxes unchecked) on both the original css and that generated by
httrack and comparing the outputs with any compare - diff program.