Gogs 1ec4058aa2 Initial configuration | 7 anni fa | |
---|---|---|
.. | ||
bin | 7 anni fa | |
src | 7 anni fa | |
.gitignore | 7 anni fa | |
.scrutinizer.yml | 7 anni fa | |
.travis.yml | 7 anni fa | |
CREDITS | 7 anni fa | |
LICENSE.txt | 7 anni fa | |
README.md | 7 anni fa | |
RELEASE.md | 7 anni fa | |
UPGRADING.md | 7 anni fa | |
composer.json | 7 anni fa | |
example.php | 7 anni fa | |
phpunit.xml.dist | 7 anni fa | |
sami.php | 7 anni fa |
The need for an HTML5 parser in PHP is clear. This project initially
began with the seemingly abandoned html5lib
project original source.
But after some initial refactoring work, we began a new parser.
Install HTML5-PHP using composer.
To install, add masterminds/html5
to your composer.json
file:
{
"require" : {
"masterminds/html5": "2.*"
},
}
(You may substitute 2.*
for a more specific release tag, of
course.)
From there, use the composer install
or composer update
commands to
install.
HTML5-PHP has a high-level API and a low-level API.
Here is how you use the high-level HTML5
library API:
<?php
// Assuming you installed from Composer:
require "vendor/autoload.php";
use Masterminds\HTML5;
// An example HTML document:
$html = <<< 'HERE'
<html>
<head>
<title>TEST</title>
</head>
<body id='foo'>
<h1>Hello World</h1>
<p>This is a test of the HTML5 parser.</p>
</body>
</html>
HERE;
// Parse the document. $dom is a DOMDocument.
$html5 = new HTML5();
$dom = $html5->loadHTML($html);
// Render it as HTML5:
print $html5->saveHTML($dom);
// Or save it to a file:
$html5->save($dom, 'out.html');
?>
The $dom
created by the parser is a full DOMDocument
object. And the
save()
and saveHTML()
methods will take any DOMDocument.
It is possible to pass in an array of configuration options when loading an HTML5 document.
// An associative array of options
$options = array(
'option_name' => 'option_value',
);
// Provide the options to the constructor
$html5 = new HTML5($options);
$dom = $html5->loadHTML($html);
The following options are supported:
encode_entities
(boolean): Indicates that the serializer should aggressively
encode characters as entities. Without this, it only encodes the bare
minimum.disable_html_ns
(boolean): Prevents the parser from automatically
assigning the HTML5 namespace to the DOM document. This is for
non-namespace aware DOM tools.target_document
(\DOMDocument): A DOM document that will be used as the
destination for the parsed nodes.implicit_namespaces
(array): An assoc array of namespaces that should be
used by the parser. Name is tag prefix, value is NS URI.This library provides the following low-level APIs that you can use to create more customized HTML5 tools:
InputStream
abstraction that can work with different kinds of
input source (not just files and strings).The unit tests exercise each piece of the API, and every public function is well-documented.
The parser is designed as follows:
InputStream
portion handles direct I/O.Scanner
handles scanning on behalf of the parser.Tokenizer
requests data off of the scanner, parses it, clasifies
it, and sends it to an EventHandler
. It is a recursive descent parser.EventHandler
receives notifications and data for each specific
semantic event that occurs during tokenization.DOMBuilder
is an EventHandler
that listens for tokenizing
events and builds a document tree (DOMDocument
) based on the events.The serializer takes a data structure (the DOMDocument
) and transforms
it into a character representation -- an HTML5 document.
The serializer is broken into three parts:
OutputRules
contain the rules to turn DOM elements into strings. The
rules are an implementation of the interface RulesInterface
allowing for
different rule sets to be used.Traverser
, which is a special-purpose tree walker. It visits
each node node in the tree and uses the OutputRules
to transform the node
into a string.HTML5
manages the Traverser
and stores the resultant data
in the correct place.The serializer (save()
, saveHTML()
) follows the
section 8.9 of the HTML 5.0 spec.
So tags are serialized according to these rules:
Please check the issue queue for a full list, but the following are issues known issues that are not presently on the roadmap:
:
has no special
meaning.
By default the parser does not support XML style namespaces via :
;
to enable the XML namespaces see the XML Namespaces section##XML Namespaces
To use XML style namespaces you have to configure well the main HTML5
instance.
use Masterminds\HTML5;
$html = new HTML5(array(
"xmlNamespaces" => true
));
$dom = $html->loadHTML('<t:tag xmlns:t="http://www.example.com"/>');
$dom->documentElement->namespaceURI; // http://www.example.com
You can also add some default prefixes that will not require the namespace declaration, but it's elements will be namespaced.
use Masterminds\HTML5;
$html = new HTML5(array(
"implicitNamespaces"=>array(
"t"=>"http://www.example.com"
)
));
$dom = $html->loadHTML('<t:tag/>');
$dom->documentElement->namespaceURI; // http://www.example.com
The dedicated (and patient) contributors of patches small and large, who have already made this library better.See the CREDITS file for a list of contributors.
We owe a huge debt of gratitude to the original authors of html5lib.
While not much of the orignal parser remains, we learned a lot from reading the html5lib library. And some pieces remain here. In particular, much of the UTF-8 and Unicode handling is derived from the html5lib project.
This software is released under the MIT license. The original html5lib library was also released under the MIT license.
See LICENSE.txt
Certain files contain copyright assertions by specific individuals involved with html5lib. Those have been retained where appropriate.