HTMLPurifier_Lexer Class Reference

Inheritance diagram for HTMLPurifier_Lexer:

Public Member Functions
	__construct ()
	parseData ($string)
	tokenizeHTML ($string, $config, $context)
	normalize ($html, $config, $context)
	extractBody ($html)
Static Public Member Functions
static	create ($config)
Data Fields
	$tracksLineNumbers = false
Static Protected Member Functions
static	escapeCDATA ($string)
static	escapeCommentedCDATA ($string)
static	removeIEConditional ($string)
static	CDATACallback ($matches)
Protected Attributes
	$_special_entity2str

---

Detailed Description

Forgivingly lexes HTML (SGML-style) markup into tokens.

A lexer parses a string of SGML-style markup and converts them into corresponding tokens. It doesn't check for well-formedness, although its internal mechanism may make this automatic (such as the case of HTMLPurifier_Lexer_DOMLex). There are several implementations to choose from.

A lexer is HTML-oriented: it might work with XML, but it's not recommended, as we adhere to a subset of the specification for optimization reasons. This might change in the future. Also, most tokenizers are not expected to handle DTDs or PIs.

This class should not be directly instantiated, but you may use create() to retrieve a default copy of the lexer. Being a supertype, this class does not actually define any implementation, but offers commonly used convenience functions for subclasses.

Note:

The unit tests will instantiate this class for testing purposes, as many of the utility functions require a class to be instantiated. This means that, even though this class is not runnable, it will not be declared abstract.

Note:

We use tokens rather than create a DOM representation because DOM would:

1. Require more processing and memory to create,
2. Is not streamable, and
3. Has the entire document structure (html and body not needed).

However, DOM is helpful in that it makes it easy to move around nodes without a lot of lookaheads to see when a tag is closed. This is a limitation of the token system and some workarounds would be nice.

Definition at line 42 of file Lexer.php.

---

Constructor & Destructor Documentation

__construct

(

)

Reimplemented in HTMLPurifier_Lexer_DOMLex.

Definition at line 142 of file Lexer.php.

---

Member Function Documentation

static CDATACallback

(

$

matches

)

[static, protected]

Callback function for escapeCDATA() that does the work.

Warning:

Though this is public in order to let the callback happen, calling it directly is not recommended. $matches PCRE matches array, with index 0 the entire match and 1 the inside of the CDATA section.

Returns:

Escaped internals of the CDATA section.

Definition at line 253 of file Lexer.php.

static create

(

$

config

)

[static]

Retrieves or sets the default Lexer as a Prototype Factory.

By default HTMLPurifier_Lexer_DOMLex will be returned. There are a few exceptions involving special features that only DirectLex implements.

Note:

The behavior of this class has changed, rather than accepting a prototype object, it now accepts a configuration object. To specify your own prototype, set Core.LexerImpl to it. This change in behavior de-singletonizes the lexer object.

Parameters:

$config

Instance of HTMLPurifier_Config

Returns:

Concrete lexer.

Definition at line 68 of file Lexer.php.

Here is the caller graph for this function:

static escapeCDATA

(

$

string

)

[static, protected]

Translates CDATA sections into regular sections (through escaping).

Parameters:

$string

HTML string to process.

Returns:

HTML with CDATA sections escaped.

Definition at line 214 of file Lexer.php.

Here is the caller graph for this function:

static escapeCommentedCDATA

(

$

string

)

[static, protected]

Special CDATA case that is especially convoluted for <script>

Definition at line 225 of file Lexer.php.

Here is the caller graph for this function:

extractBody

(

$

html

)

Takes a string of HTML (fragment or document) and returns the content

Todo:

Consider making protected

Definition at line 314 of file Lexer.php.

Here is the caller graph for this function:

normalize	(	$	html,
		$	config,
		$	context
	)

Takes a piece of HTML and normalizes it by converting entities, fixing encoding, extracting bits, and other good stuff.

Todo:

Consider making protected

Definition at line 263 of file Lexer.php.

Here is the call graph for this function:

Here is the caller graph for this function:

parseData

(

$

string

)

Parses special entities into the proper characters.

This string will translate escaped versions of the special characters into the correct ones.

Warning:

You should be able to treat the output of this function as completely parsed, but that's only because all other entities should have been handled previously in substituteNonSpecialEntities()

Parameters:

$string

String character data to be parsed.

Returns:

Parsed character data.

Definition at line 174 of file Lexer.php.

Here is the caller graph for this function:

static removeIEConditional

(

$

string

)

[static, protected]

Special Internet Explorer conditional comments should be removed.

Definition at line 236 of file Lexer.php.

Here is the caller graph for this function:

tokenizeHTML	(	$	string,
		$	config,
		$	context
	)

Lexes an HTML string into tokens.

Parameters:

$string

String HTML.

Returns:

HTMLPurifier_Token array representation of HTML.

Reimplemented in HTMLPurifier_Lexer_DOMLex, HTMLPurifier_Lexer_PEARSax3, HTMLPurifier_Lexer_DirectLex, and HTMLPurifier_Lexer_PH5P.

Definition at line 204 of file Lexer.php.

---

Field Documentation

$_special_entity2str [protected]

Initial value:

            array(
                    '"' => '"',
                    '&'  => '&',
                    '&lt;'   => '<',
                    '&gt;'   => '>',
                    '&#39;'  => "'",
                    '&#039;' => "'",
                    '&#x27;' => "'"
            )

Most common entity to raw value conversion table for special entities.

Definition at line 149 of file Lexer.php.

$tracksLineNumbers = false

Whether or not this lexer implements line-number/column-number tracking. If it does, set to true.

Reimplemented in HTMLPurifier_Lexer_DirectLex.

Definition at line 49 of file Lexer.php.

---

The documentation for this class was generated from the following file:

• C:/xampp/htdocs/moodle/lib/htmlpurifier/HTMLPurifier/Lexer.php