[tjdrico]

Hehe, fair comment. Where I live, "ass" is more likely to mean donkey than buttocks, so I don't even regard it as a candidate for censorship.

However, if it posed a problem, an administrator should be able to get round it by using 3 replacements. For example:

1. ass -> donkey

This has the undesired side-effect of changing password to "pdonkeyword" and "class" to "cldonkey". The abomination of "class" means that a lot of the CSS stuff up. However, if the admin also includes:

2. cldonkey -> class
3. pdonkeyword -> password

Then everything's fine. "ass password" gets rendered as "donkey password", and all the class= definitions in the source are also correct.

Whether an admin can be bothered to add a couple of extra replacements to "correct" any such problems really depends on how important the optional censorship is.