Quoting "m.spring@..." <m.spring@...>:
> This module raises some H::T specific issues:
> * H::T needs template files if you want to use caching - which is
> necessary as translating adds processing time but has to be done
> only once for every template. At the moment I plan to link my
> template files to country specific versions, but this will clutter
> the directory without real necessity.
> Q: What alternatives are possible?
There was talk last year some time of adding the ability to generate your own
cache key in HTML::Template. Right now it just takes the path of the template
file as the cache key, but if you could generate your own cache keys, then you
could include the path to the template file, plus any filter arguements.
I had proposed a patch to do this, and Sam mentioned that he would try to
include 'something like this' in the next release, but I guess it slipped
through the cracks. I worked around this in a different way if I remember
correctly, but I still think it would be a handy and simple addition to