in reply to Internationalization and Template::Toolkit

Personally, I would definitely consider any solution Autrijus Tang puts up. He's kinda one of those people who not only has been around the block, but he helped build the block you're trying to go around.

The nice thing about the solution in the page you mentioned is that it drops in and, other than the localizable text, the website doesn't change. This is a big improvement over other schemes I've seen, which generally involve post-processing the templates with the static text, then praying the dynamic text from the database is the right language.

Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.

  • Comment on Re: Internationalization and Template::Toolkit

Replies are listed 'Best First'.
Re^2: Internationalization and Template::Toolkit
by gaal (Parson) on Dec 01, 2004 at 17:12 UTC
    Plus, it's got a toolchain. GNU gettext msggen and friends work with it, so you can extract (and update) localizable strings, and have your translators use whatever tools they alrady like for dealing with PO files.

    (One note: if you define a gettext()/_()-like function for use in code, don't name it _ because there's a funky problem with the meaning of it. Use __ (double underscore); Autrijus' version of gettext is patched to handle it.)

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom