in reply to Re: Re: Scraping HTML: orthodoxy and reality
in thread Scraping HTML: orthodoxy and reality

For sure, this approach is expensive cpu-wise, etc., but if I need a solution that works right away then "module fetches/renders HTML into text", combined with regex processing that at least I know how to do, IS a solution. Sure, per RBFuller, "... if the solution is not beautiful, I know it is wrong" but if those cycles won't be used for anything else, who cares? This bear of little brain would have his program done.

So, assuming that efficiency doesn't matter, I'm still fishing for something like building the $html object via a LWP 'get' as above and then turning it into text that I can examine with regexen. (However, since this is turning a golden object into lead, I'll do some more digging as you suggest, like re-reading this thread's Data::Dumper/HTML::TableExtract example! :-)

  • Comment on Re: Re: Re: Scraping HTML: orthodoxy and reality

Replies are listed 'Best First'.
Re: Re: Re: Re: Scraping HTML: orthodoxy and reality
by chanio (Priest) on Jul 09, 2003 at 07:17 UTC
    I am just starting my studies with Perl, and of course, with modules I have less experience.

    But if you could print an HTML file to a plain text printer the result sent to a file would be just what you saw at the screen, right?

    Then you would treat it like text...