...you might consider the standalone version of Tidy for html...

I agree. It's very nifty indeed, easy to use and highly configurable.

Something as simple as:

my $in  = 'bad.html';
my $out = 'tidied.html';
my $err = 'tidy.err';
my $cnf = 'tidy.cnf';

system( 
  'tidy.exe',
  '-asxml',
  -config => $cnf,
  -file   => $err,
  -output => $out,
  $in,
);
[download]

can be easily adapted to process a list or even a local copy of a web site. The config file can be tweaked to be severe or lenient to taste.

You can easily interrogate all the error files to get a good picture of how bad the html is (and there is a lot of it about!).

Again, I agree. Why bother to go to a lot of trouble when there is a very clever bit of kit available.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.