> > 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..

I'll try a few things at home tonight to confirm...I 
think I have figured out the case when the log is 
written correctly...it is when you click "Finish", 
then "Exit" after the mirror completes.  Do you think 
maybe HTTrack isn't closing the log file correctly or 
at the right time (i.e. not forced to close the log 
file until 'Exit' is pushed?)

> > 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)

Just for the record there are several open source 
javascript engines, SpiderMonkey from the mozilla 
project <http://www.mozilla.org/js/spidermonkey/> that 
has been used in several non Mozilla browser projects:
<http://www.mozilla.org/js/projects.html>

Also Rhino <http://www.mozilla.org/rhino/> a Java based 
Javascript engine.

Licensing is covered here (as HTTrack is GPL):
<http://www.mozilla.org/MPL/relicensing>-
faq.html#mozilla-with-gpl

I'm thinking maybe someone (not necessarily Xavier) 
could combine the HTTrack source with the SpiderMonkey 
javascript engine.  If licensing is an issue, maybe 
the Javascript engine portion can be a module added 
afterwards by the enduser and enabled in an "Advanced" 
configuration page.  (My understanding is the engine 
can be an external DLL.)