aboutsummaryrefslogtreecommitdiffhomepage
path: root/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.LexerImpl.txt
diff options
context:
space:
mode:
Diffstat (limited to 'inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.LexerImpl.txt')
-rw-r--r--inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.LexerImpl.txt34
1 files changed, 34 insertions, 0 deletions
diff --git a/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.LexerImpl.txt b/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.LexerImpl.txt
new file mode 100644
index 00000000..e11c0152
--- /dev/null
+++ b/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.LexerImpl.txt
@@ -0,0 +1,34 @@
1Core.LexerImpl
2TYPE: mixed/null
3VERSION: 2.0.0
4DEFAULT: NULL
5--DESCRIPTION--
6
7<p>
8 This parameter determines what lexer implementation can be used. The
9 valid values are:
10</p>
11<dl>
12 <dt><em>null</em></dt>
13 <dd>
14 Recommended, the lexer implementation will be auto-detected based on
15 your PHP-version and configuration.
16 </dd>
17 <dt><em>string</em> lexer identifier</dt>
18 <dd>
19 This is a slim way of manually overridding the implementation.
20 Currently recognized values are: DOMLex (the default PHP5
21implementation)
22 and DirectLex (the default PHP4 implementation). Only use this if
23 you know what you are doing: usually, the auto-detection will
24 manage things for cases you aren't even aware of.
25 </dd>
26 <dt><em>object</em> lexer instance</dt>
27 <dd>
28 Super-advanced: you can specify your own, custom, implementation that
29 implements the interface defined by <code>HTMLPurifier_Lexer</code>.
30 I may remove this option simply because I don't expect anyone
31 to use it.
32 </dd>
33</dl>
34--# vim: et sw=4 sts=4