aboutsummaryrefslogtreecommitdiffhomepage
path: root/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Output.TidyFormat.txt
diff options
context:
space:
mode:
Diffstat (limited to 'inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Output.TidyFormat.txt')
-rw-r--r--inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Output.TidyFormat.txt25
1 files changed, 25 insertions, 0 deletions
diff --git a/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Output.TidyFormat.txt b/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Output.TidyFormat.txt
new file mode 100644
index 00000000..23dd4d3d
--- /dev/null
+++ b/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Output.TidyFormat.txt
@@ -0,0 +1,25 @@
1Output.TidyFormat
2TYPE: bool
3VERSION: 1.1.1
4DEFAULT: false
5--DESCRIPTION--
6<p>
7 Determines whether or not to run Tidy on the final output for pretty
8 formatting reasons, such as indentation and wrap.
9</p>
10<p>
11 This can greatly improve readability for editors who are hand-editing
12 the HTML, but is by no means necessary as HTML Purifier has already
13 fixed all major errors the HTML may have had. Tidy is a non-default
14 extension, and this directive will silently fail if Tidy is not
15 available.
16</p>
17<p>
18 If you are looking to make the overall look of your page's source
19 better, I recommend running Tidy on the entire page rather than just
20 user-content (after all, the indentation relative to the containing
21 blocks will be incorrect).
22</p>
23--ALIASES--
24Core.TidyFormat
25--# vim: et sw=4 sts=4