HTML::Tagset - data tables useful in parsing HTML |
HTML::Tagset - data tables useful in parsing HTML
use HTML::Tagset; # Then use any of the items in the HTML::Tagset package # as need arises
This module contains several data tables useful in various kinds of HTML parsing operations.
Note that all tag names used are lowercase.
In the following documentation, a ``hashset'' is a hash being used as a set -- the hash conveys that its keys are there, and the actual values associated with the keys are not significant. (But what values are there, are always true.)
$HTML::Tagset::emptyElement{'hr'}
exists and is true.
$HTML::Tagset::emptyElement{'dl'}
does not exist, and so is not true.
$HTML::Tagset::emptyElement{'li'}
exists and is true.
HTML::TreeBuilder
, but I include it here on the off chance that someone
might find it of use:
When we see a ``<p>'' token, we go lookup up the lineage for a p element we might have to minimize. At first sight, we might say that if there's a p anywhere in the lineage of this new p, it should be closed. But that's wrong. Consider this document:
<html> <head> <title>foo</title> </head> <body> <p>foo <table> <tr> <td> foo <p>bar </td> </tr> </table> </p> </body> </html>
The second p is quite legally inside a much higher p.
My formalization of the reason why this is legal, but this:
<p>foo<p>bar</p></p>
isn't, is that something about the table constitutes a ``barrier'' to the application of the rule about what p must minimize.
So @HTML::Tagset::p_closure_barriers
is the list of all such
barrier-tags.
You may find it useful to alter the behavior of modules (like
HTML::Element
or HTML::TreeBuilder
) that use HTML::Tagset
's
data tables by altering the data tables themselves. You are welcome
to try, but be careful; and be aware that different modules may or may
react differently to the data tables being changed.
Note that it may be inappropriate to use these tables for producing
HTML -- for example, %isHeadOrBodyElement
lists the tagnames
for all elements that can appear either in the head or in the body,
such as ``script''. That doesn't mean that I am saying your code that
produces HTML should feel free to put script elements in either place!
If you are producing programs that spit out HTML, you should be
intimately familiar with the DTDs for HTML or XHTML (available at
http://www.w3.org/
), and you should slavishly obey them, not
the data tables in this document.
the HTML::Element manpage, the HTML::TreeBuilder manpage, the HTML::LinkExtor manpage
Copyright 1995-2000 Gisle Aas; copyright 2000 Sean M. Burke.
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
Current maintainer: Sean M. Burke, <sburke@cpan.org>
Most of the code/data in this module was adapted from code written by
Gisle Aas <gisle@aas.no> for HTML::Element
,
HTML::TreeBuilder
, and HTML::LinkExtor
.
HTML::Tagset - data tables useful in parsing HTML |