Am 18.07.2006 um 18:06 schrieb Daniel Poelzleithner:
>
> Malcolm Tredinnick wrote:
>
>> Damn. Your phrasing tipped me off to a case we need this more: RSS
>> feeds
>> and Atom content elements with type="html". :-(
>>
>> We might need a "mark as unsafe" filter for these cases (so that
>> {{ var|
>> escape|unsafe|escape }}) works (or just make "escape" not mark the
>> string as safe, but I suspect that will have unintended annoying
>> side-effects).
>
> I suggest {{var|escape|escape:force}}
>
> force as an optional argument to escape already escaped strings.
'force' is nice! But a string as an argument that modifies the
function feels a bit dirty.
How about calling it 'forced_escape'? Like
{{ var | escape | forced_escape }}
That's much better to read than
{{ var | escape | mark_unsafe | escape }}
... which is just mind twisting (huh? They escape? mark it as unsafe?
escape again?
what was this crazy programmer smoking, man ...)
>
> But an unsafe filter may be usefull, too.
Not sure. And you can still write one for your own usage, it's trivial.
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
-~----------~----~----~----~------~----~------~--~---
