I thoroughly agree. That doesn't change the fact that many managers *don't* agree, and writing code to change "foo" to "*$@" will sometimes pay the rent for you and your children. I'm glad I convinced my managers to let the *recipient* choose the filter settings, and not try to impose their sensitivities on everyone else.

The scheme I wrote was pretty effective at finding creative alternative glyphic forms, like $.h.1.+. Some kids played with the boundaries of what the filter could and could not do, but the average everyday slips of decorum were found and scrubbed.

For the most part, it solved the problem put to management: that casual swearing was filtered if individual users wanted it to be filtered.

--
[ e d @ h a l l e y . c c ]

In reply to Re: Re: regex for swear filter by halley
in thread regex for swear filter by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • 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:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.