comment on

Obligatory Zalgo-summoning solution:

#!/usr/bin/perl -p0
s/<!([^<>]|<(?1)*>)*>//gs;
s/<(?!div\b[^>]*\bclass\s*=\s*(['"])data\1)([^<>]|<(?2)*>)*>//gs;
s/.*?<(?:[^'"]|(['"]).*?\1)*?\bid\s*=\s*(['"])(.*?)\2.*?>([^<]*)/$3=$4
+, /gs;
s/&#(\w+);/chr $1/ge;
s/[^\w=, ]|, $|(.)\1\1//g;
[download]

To make it harder on regexes, I suggest:

throwing unbalanced [<>'"] inside CDATA sections / comments / attributes (especially class='data"')
using names that can be confused with the interesting ones: <divx, aclass="data", …
using XML namespaces liberally
using external entities

In reply to Re: Parsing HTML/XML with Regular Expressions by Grimy
in thread Parsing HTML/XML with Regular Expressions by haukex

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.


Problems? Is your data what you think it is?
	PerlMonks