Daniel Ziegenberg
be7f6d4834
Prior to this change, all the line endings in the imported HTMLPurifier library were using CRLF (\r\n aka Windows style), but the HTMLPurifier source and also the downloadable artefacts use LF (\n aka Linux style) as line endings. This has been the case since510d190382when with the commit "MDL-38672 import HTML Purifier 4.5.0" all line endings were changed from LF to CRLF. There was no comment in the commit on why this change was done. As the original source uses LF, this commit partly reverts510d190382and goes back to LF as line endings. Signed-off-by: Daniel Ziegenberg <daniel@ziegenberg.at>
35 lines
1.0 KiB
Plaintext
35 lines
1.0 KiB
Plaintext
Core.LexerImpl
|
|
TYPE: mixed/null
|
|
VERSION: 2.0.0
|
|
DEFAULT: NULL
|
|
--DESCRIPTION--
|
|
|
|
<p>
|
|
This parameter determines what lexer implementation can be used. The
|
|
valid values are:
|
|
</p>
|
|
<dl>
|
|
<dt><em>null</em></dt>
|
|
<dd>
|
|
Recommended, the lexer implementation will be auto-detected based on
|
|
your PHP-version and configuration.
|
|
</dd>
|
|
<dt><em>string</em> lexer identifier</dt>
|
|
<dd>
|
|
This is a slim way of manually overridding the implementation.
|
|
Currently recognized values are: DOMLex (the default PHP5
|
|
implementation)
|
|
and DirectLex (the default PHP4 implementation). Only use this if
|
|
you know what you are doing: usually, the auto-detection will
|
|
manage things for cases you aren't even aware of.
|
|
</dd>
|
|
<dt><em>object</em> lexer instance</dt>
|
|
<dd>
|
|
Super-advanced: you can specify your own, custom, implementation that
|
|
implements the interface defined by <code>HTMLPurifier_Lexer</code>.
|
|
I may remove this option simply because I don't expect anyone
|
|
to use it.
|
|
</dd>
|
|
</dl>
|
|
--# vim: et sw=4 sts=4
|