Name	Size	Mode	Actions
extras/	-	0755	rm
library/	-	0755	rm
maintenance/	-	0755	rm
plugins/	-	0755	rm
tests/	-	0755	rm
composer.json	640	0644	editdlrm
CREDITS	341	0644	editdlrm
INSTALL	14083	0644	editdlrm
INSTALL.fr.utf8	1899	0644	editdlrm
LICENSE	26456	0644	editdlrm
NEWS	63902	0644	editdlrm
package.php	1762	0644	editdlrm
phpdoc.ini	4042	0644	editdlrm
README.md	1242	0644	editdlrm
release1-update.php	2670	0644	editdlrm
release2-tag.php	532	0644	editdlrm
test-settings.sample.php	2706	0644	editdlrm
test-settings.travis.php	2593	0644	editdlrm
TODO	6832	0644	editdlrm
VERSION	6	0644	editdlrm
WHATSNEW	734	0644	editdlrm
WYSIWYG	857	0644	editdlrm

WYSIWYG - What You See Is What You Get HTML Purifier: A Pretty Good Fit for TinyMCE and FCKeditor Javascript-based WYSIWYG editors, simply stated, are quite amazing. But I've always been wary about using them due to security issues: they handle the client-side magic, but once you've been served a piping hot load of unfiltered HTML, what should be done then? In some situations, you can serve it uncleaned, since you only offer these facilities to trusted(?) authors. Unfortunantely, for blog comments and anonymous input, BBCode, Textile and other markup languages still reign supreme. Put simply: filtering HTML is hard work, and these WYSIWYG authors don't offer anything to alleviate that trouble. Therein lies the solution: HTML Purifier is perfect for filtering pure-HTML input from WYSIWYG editors. Enough said. vim: et sw=4 sts=4