Hmm. I see two different cases that get munched in the discussion:
a) You run data through some filter or inside a html tag where it shouldn't be
escaped.
For this, you (or the designer) need to specify this in the template.
b) Parts of the context are pre-assembled html or are already unescaped. The
designer can't
always know when this is the case.
To cope with this, I really like the approach of Ian Bicking's Quixote:
Everything that has already been escaped is packaged in a wrapper class,
so that you pass something like
HtmlEscaped('<a href="..">bla</a>')
into the context.
Michael
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
