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>
16 lines
767 B
Plaintext
16 lines
767 B
Plaintext
Core.Encoding
|
|
TYPE: istring
|
|
DEFAULT: 'utf-8'
|
|
--DESCRIPTION--
|
|
If for some reason you are unable to convert all webpages to UTF-8, you can
|
|
use this directive as a stop-gap compatibility change to let HTML Purifier
|
|
deal with non UTF-8 input. This technique has notable deficiencies:
|
|
absolutely no characters outside of the selected character encoding will be
|
|
preserved, not even the ones that have been ampersand escaped (this is due
|
|
to a UTF-8 specific <em>feature</em> that automatically resolves all
|
|
entities), making it pretty useless for anything except the most I18N-blind
|
|
applications, although %Core.EscapeNonASCIICharacters offers fixes this
|
|
trouble with another tradeoff. This directive only accepts ISO-8859-1 if
|
|
iconv is not enabled.
|
|
--# vim: et sw=4 sts=4
|