You might also consider HTML::TableExtract, which is somewhat more complicated, but also (as far as I can tell from skimming the TableContentParser POD) appears substantially more powerful than HTML::TableContentParser (in that it handles nested tables, for instance). It's also actively maintained, which TableContentParser does not appear to be.