Max Battcher wrote:
> > the standard solution is to use a wrapper for strings that you
> > *don't* want escaped. see e.g. the section on "HTML templates"
> > on this page:
>
> The other problem is that not everyone wants the same escape. For
> instance, there are those of us that {% load markup %} and then
> |restructuredtext (or |markdown or |textile) just about everything,
> and auto-HTML escape could certainly cause havoc here.
such filters should of course wrap their return values before returning
them.
</F>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers
-~----------~----~----~----~------~----~------~--~---
