According to Malcolm Austen: > On Thu, 3 Jan 2002, Gilles Detillieux wrote: > + However, the RFC does seem to be addressing any embedded white space, > + not just leading or trailing space. Does anyone else have any thoughts > + about how htdig ought to deal with these non-conforming URLs? > > Well Gilles, that certainly convinced me that htdig is doing the right > thing. The problem is clearly in the page that contains an href with a > significant space character that has not been escaped to %20 ... htdig > doesn't need to mishandle the situation just because a web editor and/or a > browser does!
OK, I was just a bit concerned that this mishandling was common enough that we'd have to do something about it. We've had to tweak the HTML parser many time in the past to handle non-conforming code. There's just a lot of bad HTML out there. However, if this problem isn't too pervasive, I'd just as soon maintain the status quo in htdig. -- Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil Dept. Physiology, U. of Manitoba Phone: (204)789-3766 Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930 _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html
