HTML parser class
Objects of the HTML::Parser class will recognize markup and separate it
from plain text (alias data content) in HTML documents. As different
kinds of markup and text are recognized, the corresponding event handlers
are invoked.
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.
The document to be parsed may be supplied in arbitrary chunks. This makes
on-the-fly parsing as documents are received from the network possible.
If event driven parsing does not feel right for your application, you might
want to use HTML::PullParser. This is an HTML::Parser subclass that allows
a more conventional program structure.
- Developed at devel:languages:perl
- Sources inherited from project openSUSE:Factory
-
6
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Backports:SLE-15-SP4:FactoryCandidates/perl-HTML-Parser && cd $_ - Create Badge
Source Files
| Filename | Size | Changed |
|---|---|---|
| HTML-Parser-3.69.tar.gz | 0000089531 87.4 KB | |
| perl-HTML-Parser.changes | 0000009079 8.87 KB | |
| perl-HTML-Parser.spec | 0000003064 2.99 KB |
Revision 23 (latest revision is 42)
Sascha Peilicke (saschpe)
accepted
request 88224
from
Vítězslav Čížek (vitezslav_cizek)
(revision 23)
- update to 3.69
Documentation fix; encode_utf8 mixup [RT#71151]
Make it clearer that there are 2 (actually 3) options for handing "UTF-8 garbage"
Github is the official repo
Can't be bothered to try to fix the failures that occur on perl-5.6
fix to TokeParser to correctly handle option configuration
Aesthetic change: remove extra ;
Trim surrounding whitespace from extracted URLs.
_______________________________________________________________________________
Comments 0