Talk:Comparison of HTML parsers

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Computing  
WikiProject icon This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
 ???  This article has not yet received a rating on the project's quality scale.
 ???  This article has not yet received a rating on the project's importance scale.

Please check/review column definitions[edit]

The softwate, a "HTML parser"... DOM with a LoadHTML method is a "HTML parser"!? There are some standalone software, that only transform HTML; and "enabled" to programmer's to traversal all nodes, etc.? What the software taxonomy here??
Implementation language(s)
Ok, but not confuse with "driver/bridge for bin implementation".
Latest date
Latest release date of significant changes in the implementation source code.
HTML Parsing
Common sense says that all "HTML parsers" have YES to "HTML Parsing"... So, same problem, of column "Parser": DOMDocument class with a LoadHTML method is a "enabled" to programmer's "HTML parsing"!?
Clean HTML
sanitize (generating standard-compatible web-page, reduce spam, etc.) and clean (strip out surplus presentational tags, remove XSS code, etc.) HTML code
Update HTML
Updates HTML4.X to XHTML or to HTML5, converting deprecated tags (ex. CENTER) to valid ones (ex. DIV with style="text-align:center;").

It is a consensus here? --Krauss (talk) 13:20, 9 June 2013 (UTC)

HTML Parsing column with arbitrary Yes or No (I don't get what the author means by saying that HTML parser does not parse HTML?) looks like original research. Actually all the table does not have sources and just should be deleted according to the Wikipedia rules --Ilya (talk) 09:29, 5 May 2015 (UTC)

Other parsers that are not listed in the article[edit]

In case anyone is interested and has enough time to add them, at the end of Beautiful Soup documentation are linked the following parsers:

  • Rubyful Soup: port of Beautiful Soup to Ruby.
  • Hpricot: written in Ruby and C (currently its development is discontinued).
  • ElementTree: fast Python XML parser (last updated in September 2007).
  • HtmlPrag: Scheme library for parsing bad HTML (source code here).
  • xmltramp: a "standard" XML/XHTML parser. Like most parsers, it makes you traverse the tree yourself, but it's easy to use.
  • pullparser includes a tree-traversal method. Today is unmaintained (now part of mechanize, but interface no longer public).
  • Mike Foord didn't like the way Beautiful Soup can change HTML if you write the tree back out, so he wrote HTML Scraper. It's basically a version of HTMLParser that can handle bad HTML (published in 2004 and posibly obsolete).
  • Ka-Ping Yee's combines page scraping with URL opening.

Reviewing the history of the discussion also can be seen that in this edition someone else suggested htmLawed (PHP alternative to Tidy).-- (talk) 07:20, 5 December 2014 (UTC)