On Fri, Feb 27, 2009 at 11:59 PM, Tim Chase <django.us...@tim.thechases.com> wrote: > >>> The COMMENTS_ALLOW_PROFANITIES setting is undocumented at >>> http://docs.djangoproject.com/en/dev/ref/contrib/comments/settings/ >> >> A known omission, with a purpose: >> >> http://code.djangoproject.com/ticket/9530 >> http://code.djangoproject.com/ticket/8794 > > If the preference is to prevent distributing plaintext > profanities, would a simple tweak be to distribute a ROT13 > version? It's easy to decode on the fly, or even in the > distribution:
The problem isn't the fact that it's in plaintext - its the profanities list itself. Profanity detection isn't something you can do with a simple match list - at least, not if you want to do it well (hence, the Scunthorpe problem). The goal is to deprecate the profanity list - the only issues are when, and how we do this in a backwards compatible way. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
