Jump to content

Talk:Comparison of HTML parsers

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Paul da programmer (talk | contribs) at 18:26, 8 February 2018 (Please check/review column definitions). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
WikiProject iconComputing Unassessed
WikiProject iconThis 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 Wikipedia's content assessment scale.
???This article has not yet received a rating on the project's importance scale.

Please check/review column definitions

Parser
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??
License
Ok.
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;").
Need to add Javascript compatibility column as some libraries support javascript and some don't.

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

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)[reply]

Other parsers that are not listed in the article

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 scrape.py 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).--200.45.200.41 (talk) 07:20, 5 December 2014 (UTC)[reply]

Hello fellow Wikipedians,

I have just modified 2 external links on Comparison of HTML parsers. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 16:24, 11 August 2017 (UTC)[reply]