On Fri, 18 Apr 2008, Peter Lukezic wrote:
> My Problem is, when using this function, I need the raw output of this
> function and I always get it with full html entities like '<select
> name="...' - ok I think I could use the function like {raw
> (formSelect(...))} but I don not want to do this like that. Has anyone an
> idea how to solve my problem?
I don't think that's currently possible, and honestly - I don't think we
should allow it. The reason to require raw is not only for escaping
HTML, as the template language is not only made for HTML - but also for
other contexts (such as e-mail). Requiring raw means that the designer
of the template thought about different contexts, as well as the
possibility that this code might not be HTML-safe. Besides this, I don't
really know if it is possible to do this (by adding another flag to the
function definition f.e.) because of the internals of the engine. I
would like to know what other people think here before continuing to
investigate this.
regards,
Derick
--
Components mailing list
[email protected]
http://lists.ez.no/mailman/listinfo/components
