::  Posts  ::  RSS  ::  ◂◂RSS  ::  Contact

Parsing HTML With Regular Expressions

February 22nd, 2013
html, tech  [html]
Perhaps you need to get some information out of HTML. Regular expressions look promising, but you get stuck so you ask for help. A typical response would be:
HTML parsing is not possible with regular expressions, since it depends on matching the opening and the closing tag. Regular expressions can only match regular languages but HTML is a context-free language.
This is true, but only in a sense so narrow it's useless. When someone asks about "regular expressions" they don't mean the restricted computer science kind but the implementations available in various programming languages. Those are much more powerful, capable of parsing HTML.

Here again we're using dangerously precise words. When someone says "HTML" they don't mean HTML as defined by the spec but HTML that they are likely to encounter in the real world. Which means you might need to handle monstrosities like "<i>italic <b>bold-italic</i> bold</b>" which have no parse tree but your browser still renders as italic bold-italic bold. [1]

But again with the precision! For typical tasks you don't need to 'parse' HTML, just extract some information from it. Regular expressions and other ad-hoc techniques can do that well and are likely to be less trouble in practice [2] than trying to use a parser.

(Because mod_pagespeed needs to make context-dependent changes to arbitrary web pages, regular expressions are not a good fit. You might think using the parsing code from a web browser would work well, but it turns out that browsers mix HTML-parsing with HTML-cleanup [1]. So pagespeed instead goes token-by-token, triggering callbacks for start and end tags.)


[1] Webkit turns <i>italic <b>bold-italic</i> bold</b> into <i>italic <b>bold-italic</b></i> <b>bold<b> at an early stage of interpreting the page.

[2] The advice to use an XML parser is just bad, as funny as the author is. XML parsers get to assume they're only going to be given valid XML and just reject anything that isn't. Extremely few pages are (or even try to be) XML, so your XML parser isn't going to be helpful.

Comment via: google plus, facebook, hacker news

Recent posts on blogs I like:

Transfers from Infrequent to Frequent Vehicles

Imagine yourself taking a train somewhere, and imagine the train is big and infrequent. Let’s say it’s the commuter train from New York down the Northeast Corridor to Newark Airport, or perhaps a low-cost OuiGo TGV from Lyon to Paris. Now imagine that you…

via Pedestrian Observations January 20, 2020

Veganism and restrictive eating

I’m reading the book Intuitive Eating, which I highly recommend. I was looking for something like it that could get me back to trusting my biological hunger without worrying that I need to control myself or my weight. It’s raised my consciousness to the w…

via Holly Elmore January 17, 2020

Algorithms interviews: theory vs. practice

When I ask people at trendy big tech companies why algorithms quizzes are mandatory, the most common answer I get is something like "we have so much scale, we can't afford to have someone accidentally write an O(n^2) algorithm and bring the site d…

via Posts on Dan Luu January 5, 2020

more     (via openring)

More Posts:


  ::  Posts  ::  RSS  ::  ◂◂RSS  ::  Contact