Re: Parsing HTML with tags intact

Your "html" is just a touch odd. It contains two obvious departures from valid html.

The data provided lacks a <body>...<body> tag pair and <bold_text> isn't an html tag at all.

Is what you posted merely a misguided, fanciful illustration or are you actually confronted with such data?

Comment on Re: Parsing HTML with tags intact Select or Download Code

Replies are listed 'Best First'.
Re^2: Parsing HTML with tags intact by mr_p (Scribe) on Jan 07, 2011 at 13:51 UTC
I can have misguided data as such. I have to be able to handle such data.	[reply]
Re^3: Parsing HTML with tags intact by ww (Archbishop) on Jan 07, 2011 at 14:17 UTC
In that case, `perldoc -f HTML::Parser` raises the question (for me, anyway): "Is H::P the appropriate tool? "HTML::Parser" is not a generic SGML parser. We have tried to make it able to deal with the HTML that is actually "out there", and it normally parses as closely as possible to the way the popular web browsers do it instead of strictly following one of the many HTML specifications from W3C. Where there is disagreement, there is often an option that you can enable to get the official behaviour." But I have yet to see a browser that will treat `<bold_text>` as a tag, rather than simply ignoring it (and merely rendering the enclosed text without additional formatting. Update: The doc does -- again, to me and YMMV -- suggest that you could tweak your script to deal with some of the invalid tag-like entries: $p->strict_names $p->strict_names( $bool ) By default, almost anything is allowed in tag and attribute names. This is the behaviour of most popular browsers and allows us to parse some broken tags with invalid attribute values like: <IMG SRC=newprevlstGr.gif ALT=PREV LIST BORDER=0> By default, "LIST]" is parsed as a boolean attribute, not as part of the ALT value as was clearly intended. This is also what Mozilla sees. The official behaviour is enabled by enabling this attribute. If enabled, it will cause the tag above to be reported as text since "LIST]" is not a legal attribute name. "What may be possible" and "what's provided by this node" are -- however -- two different things. :-\	[reply] [d/l] [select]