I agree with you. The only problem, as already mentionned in the previous anwers is that regexps do a terrible job at matching curse words. They are inneficient and not accurate at all.
I guess the only efficient solution here is that curse words should be tagged as such, then a quick XML filter would get rid of then easily. The author could even provide for milder alternatives, so the filter could accuratelly replace the bad language with a nicer version.
<p>Go <curse level="very offensive" cats="sexual contorsionnism" alt=" +play with your toys">f**k yourself</curse> you <curse level="quite offensive" cats="body_part" alt="bad person +">a*sh**e</curse>!
Easy isn't it?
Seriously filters don't work, be they for URL's or for words, so please let's not go there. I haven't seen much cursing around here anyway so why bother?
In reply to (silly) Re: Language Filter
by mirod
in thread Language Filter
by elusion
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |