I had a similar project and I wound up using HTML::Treebuilder. Since I'm not familiar with HTML::Parser, I'm not sure if this is better or worse than your approach.

With Treebuilder, you do apperations on html viewed as a tree. You identify the elements you want with the $element->lookdown method, specifying criteria. For simple criteria, this can just be tag is blee, attribute a is bloo, attribute b is blah. For more complicated criteria you can write a subroutine.

Then you build up the replacement html with another subroutine, and do the replacement with $element->replace(new element). I'm not looking at the perldoc as I write this so I probably made some mistakes on the syntax, but that's the general idea.

Worked for me!

In reply to Re: Getting to grips with HTML::Parser by tphyahoo
in thread Getting to grips with HTML::Parser by wfsp

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.