> Sorry for taking your time, but is there any place 
we 
> can see the status regarding these issues with 
> HTTrack?  (Possibly a new page on www.httrack.com 
for 
> planned fixes?)

Hum, might be a good idea, among with 'Common problems 
troubleshooting' (even if this is mainly in the FAQ)

> 1.) lost/missing hts-log.txt files, referenced here:
> <http://forum.httrack.com/readmsg.php?>>; id=1615&pid=196&days=14&js=1&lang=en

Could never reproduce the issue (which wasn't reported 
before), and I REALLY don't know where can be the 
problem, as the logs are written using regular fprintf
() function calls and the stream is being flushed 
using fflush() - that's all, no other specific tricks..

> 2.) priority of external link processing...making it 
> subject to the scan filters and 'get non-html 
objects 
> near page', instead of the current status that it 
> overrides those. Referenced here:
> <http://forum.httrack.com/readmsg.php?>>;
id=1603&pid=1601&days=14&js=1&lang=en

Well.. added on the TODO list (I'll check that among 
with the gz problem)

> 3.) real javascript engine inclusion/implementation 
> status/plans, referenced here:

NO plans yet, and certainly no plan in the future, as 
it would require to implement a javascript engine, 
which is really beyond the scope of an offline browser 
(I don't want HTTrack to grow to +10MB)

> 4.) The page <http://www.httrack.com/page6.php> is 
much 
> newer and more updated than 
> <http://www.httrack.com/history.txt> (linked from 
> <http://www.httrack.com/HelpHtml/>)

Fixed

> 5.) (this is just here for completeness, as you've 
> already mentioned it'll be addressed/fixed for the 
> next release :) HTTrack downloads .gz but does not 
> save.

Right, should be fixed soon ;)