I got an off list suggestion of using the eval filter ( which in 2+ years of using tt I had never noticed existed. )
so that it was something like this: [% LANG_WELCOME | eval %] I assume that this would defeating caching in the sense that, we would cache everything pre-eval but there is no mechanism to do caching thereafter. To summarize the thought in my head: eval is good if you have a limited amount of content that will pass through it. whereas probably 90% of our tags will go through the language filtering first so having two templates ( even if one is auto-generated per previous emails on this ) would be much better because you can take advantage of tt caching when running a persistent engine. Correct? _______________________________________________ templates mailing list templates@template-toolkit.org http://mail.template-toolkit.org/mailman/listinfo/templates
