HTML::Template

I worked on a product which was translated into 6 languages; we supplied 
templates in ASCII and used TMPL_VAR's to output the appropriate 
UTF8-encoded string.

ie: there are no real problems if your templates are just layouts and 
the content is provided by TMPL_VAR's.

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.

Mathew

H. Tan-Tenn wrote:
> Having read
>
> "how to use UTF8?":
> http://www.arcknowledge.com/gmane.comp.lang.perl.modules.html-template/2004-07/msg00008.html
>
> the reformist "templates in UTF-8 (and generic support for PerlIO layers)":
> http://www.arcknowledge.com/gmane.comp.lang.perl.modules.html-template/2003-06/msg00011.html
>
> and the pessimistic "No way to deal with multi-bytes characters":
> http://rt.cpan.org/Public/Bug/Display.html?id=18910
>
> I am curious to learn what is the current best practice for those of us
> desperately dependent on UTF-8 (in my case Unicode is required to
> display my languages).
>
> Thanks.
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Html-template-users mailing list
> Html-template-users@...
> https://lists.sourceforge.net/lists/listinfo/html-template-users
>

On Wed, 21 Mar 2007, Mathew Robertson wrote:

> 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?

-sam

>> 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 
talking about.

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.

Mathew