>> As an aside, there are a number of different techniques used to get
>> the UTF8 strings into the templates, eg: TMPL_VAR's, hacks to H::T,
>> using H::T::E with a callback.
> Why would you need a hack to get UTF8 strings into the templates? Is
> there a bug I should be fixing here?
ahh - my bad - I should have been *much* more clear about what I was
Often the requirement for needing UTF8 is to be able to translate a
website into multiple languages, while using the existing templates.
One problem with this is that the static text within the template is
that it wont be translated into the target language. One solution is
simply to get the template translated - however this means that each
time the sites' layout changes, the new templates need to be translated
again. An alternate solution is to store the static text within the
application, then use TMPL_VAR's to output the text - thus allowing
lookup of the static, into the target language.