diff options
Diffstat (limited to 'inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.Encoding.txt')
-rw-r--r-- | inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.Encoding.txt | 15 |
1 files changed, 0 insertions, 15 deletions
diff --git a/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.Encoding.txt b/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.Encoding.txt deleted file mode 100644 index 89e2ae34..00000000 --- a/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.Encoding.txt +++ /dev/null | |||
@@ -1,15 +0,0 @@ | |||
1 | Core.Encoding | ||
2 | TYPE: istring | ||
3 | DEFAULT: 'utf-8' | ||
4 | --DESCRIPTION-- | ||
5 | If for some reason you are unable to convert all webpages to UTF-8, you can | ||
6 | use this directive as a stop-gap compatibility change to let HTML Purifier | ||
7 | deal with non UTF-8 input. This technique has notable deficiencies: | ||
8 | absolutely no characters outside of the selected character encoding will be | ||
9 | preserved, not even the ones that have been ampersand escaped (this is due | ||
10 | to a UTF-8 specific <em>feature</em> that automatically resolves all | ||
11 | entities), making it pretty useless for anything except the most I18N-blind | ||
12 | applications, although %Core.EscapeNonASCIICharacters offers fixes this | ||
13 | trouble with another tradeoff. This directive only accepts ISO-8859-1 if | ||
14 | iconv is not enabled. | ||
15 | --# vim: et sw=4 sts=4 | ||