mirror of
https://github.com/ezyang/htmlpurifier.git
synced 2024-11-09 23:28:42 +00:00
[1.1.1]
- Clarify usage of %Core.TidyFormat - Add test-settings.sample.php, to facilitate benchmark and unit test running git-svn-id: http://htmlpurifier.org/svnroot/htmlpurifier/trunk@456 48356398-32a2-884e-a903-53898d9a118a
This commit is contained in:
parent
24663d65ed
commit
1fa5101511
6
NEWS
6
NEWS
@ -7,6 +7,12 @@ NEWS ( CHANGELOG and HISTORY ) HTMLPurifier
|
|||||||
1.1.1, unknown projected release date
|
1.1.1, unknown projected release date
|
||||||
- Various documentation updates
|
- Various documentation updates
|
||||||
- Fixed parse error in configuration documentation script
|
- Fixed parse error in configuration documentation script
|
||||||
|
- Fixed fatal error in benchmark scripts, slightly augmented
|
||||||
|
- As far as possible, whitespace is preserved in-between table children
|
||||||
|
- Configuration option to optionally Tidy up output for indentation to make up
|
||||||
|
for dropped whitespace by DOMLex (pretty-printing for the entire application
|
||||||
|
should be done by a page-wide Tidy)
|
||||||
|
- Sample test-settings.php file included
|
||||||
|
|
||||||
1.1.0, released 2006-09-16
|
1.1.0, released 2006-09-16
|
||||||
- Made URI validator more forgiving: will ignore leading and trailing
|
- Made URI validator more forgiving: will ignore leading and trailing
|
||||||
|
@ -26,14 +26,16 @@ HTMLPurifier_ConfigSchema::define(
|
|||||||
// extension constraints could be factored into ConfigSchema
|
// extension constraints could be factored into ConfigSchema
|
||||||
HTMLPurifier_ConfigSchema::define(
|
HTMLPurifier_ConfigSchema::define(
|
||||||
'Core', 'TidyFormat', false, 'bool',
|
'Core', 'TidyFormat', false, 'bool',
|
||||||
'Determines whether or not to run Tidy on the final output for pretty '.
|
'<p>Determines whether or not to run Tidy on the final output for pretty '.
|
||||||
'formatting reasons, such as indentation and wrap. This can greatly '.
|
'formatting reasons, such as indentation and wrap.</p><p>This can greatly '.
|
||||||
'improve readability for editors who are hand-editing the HTML, but is '.
|
'improve readability for editors who are hand-editing the HTML, but is '.
|
||||||
'by no means necessary as HTML Purifier has already fixed all major '.
|
'by no means necessary as HTML Purifier has already fixed all major '.
|
||||||
'errors the HTML may have had and could potentially result in data loss '.
|
'errors the HTML may have had. Tidy is a non-default extension, and this directive '.
|
||||||
'due to bugs in Tidy. Tidy is a non-default extension, and this directive '.
|
'will silently fail if Tidy is not available.</p><p>If you are looking to make '.
|
||||||
'will silently fail if Tidy is not available. This '.
|
'the overall look of your page\'s source better, I recommend running Tidy '.
|
||||||
'directive was available since 1.1.1.'
|
'on the entire page rather than just user-content (after all, the '.
|
||||||
|
'indentation relative to the containing blocks will be incorrect).</p><p>This '.
|
||||||
|
'directive was available since 1.1.1.</p>'
|
||||||
);
|
);
|
||||||
|
|
||||||
/**
|
/**
|
||||||
|
17
test-settings.sample.php
Normal file
17
test-settings.sample.php
Normal file
@ -0,0 +1,17 @@
|
|||||||
|
<?php
|
||||||
|
|
||||||
|
// This file is necessary to run the unit tests and profiling
|
||||||
|
// scripts.
|
||||||
|
|
||||||
|
// Is PEAR available on your system? If it isn't, set to false. If PEAR
|
||||||
|
// is not part of the default include_path, add it.
|
||||||
|
$GLOBALS['HTMLPurifierTest']['PEAR'] = true;
|
||||||
|
|
||||||
|
// How many times should profiling scripts iterate over the function? More runs
|
||||||
|
// means more accurate results, but they'll take longer to perform.
|
||||||
|
$GLOBALS['HTMLPurifierTest']['Runs'] = 2;
|
||||||
|
|
||||||
|
// Where is SimpleTest located?
|
||||||
|
$simpletest_location = '/path/to/simpletest/';
|
||||||
|
|
||||||
|
?>
|
Loading…
Reference in New Issue
Block a user