Hi,

I must first of all congratulate you on a great 
program.  I've been using it since the 2.x versions, 
and it just keeps getting better.

I discovered what appears to be a parsing bug in 
version 3.03.  It occurs when a link to a URL has a 
leading space.  An example can be found in the page 
<http://angelfire.com/ca7/ewot/books/tgh/ch7.html> .  
This page contains the link

<a href=" 
<http://hugin.imat.com/jordan/1_dark/1.4_whats-up>-
dark/1.4.2_slayer.html">FAQ, Section 1.4.2</a>

which has a leading space in " <http://...">;.

This results in HTTrack trying to download the wrong 
URL, as can be seen by the resulting error message:

Error:  "Not Found" (404) at link 
angelfire.com/ca7/ewot/books/tgh/%
20http://hugin.imat.com/jordan/1_dark/1.4_whats-up-
dark/1.4.2_slayer.html (from 
angelfire.com/ca7/ewot/books/tgh/ch7.html)

I don't know if the leading space is RFC compliant, 
but both IE and Netscape correctly interpret the link, 
so it would be nice to see HTTrack do the same.

Mike