Hi Robert, Could it be (parsing stop in default spider progress window) because the buffer is too small? I've noticed that is happens if the 'limit' is increased.
Enclosed is the log file. Pls let me know if you have any questions. -Partha -----Original Message----- From: Robert O'Connor [mailto:[EMAIL PROTECTED]] Sent: Friday, September 20, 2002 11:33 AM To: [EMAIL PROTECTED] Subject: Re: Feedback/Bugs for plucker and Plucker desktop. On 20 Sep 2002 at 8:28, Kundu, Partha wrote: > In the new Windows desktop, I have noticed that if I set the 'spider > progress' window to the default, the parsing hangs after a while (almost in > all web pages with any level of complex content such as www.cnn.com etc.). > However, if I send the ' spider progress' to a Console (DOS) window, the > parsing/conversion completes successfully! > Bizarre but true! Might be worth fixing/looking into. Hi Partha, I've opened a bug report on this a few days back. It would be helpful to add in to the bug report, where it stops (set verbosity to max). The one I have seen is on wired. It is bizarre, since it is just a piping of stderr from a process. It seemed to be from a certain gif image conversion, on wired. > Another thing: when parsing, I can't seem to get any images across. Always > says "not fetching image http://blah .... > > Any idea why images don't seem to come across? You likely have an exclusion set on it, for example a stayondomain, and the images are located on a different server (wired, for example puts images on a different server). Best wishes, Robert _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
PlkrLog_2002-09-20_134236.ZIP
Description: Binary data
