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
<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
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?
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||