I use TT for generating email. Unlike many our our web pages where often there are not that many strings to localize (I just use [% loc( 'Log out' ) %]), the email templates are almost entirely text. So, it doesn't make a lot of sense to use a loc() call around every paragraph or sentence.
So, what I do instead is use the Locale::Maketext-type of approach and set my TT include path with a list of language_country codes from specific to less and set up a directory hierarchy of templates where I might search templates/email/es/es_es/, templates/email/es/, and then fallback to templates/email/en. That seems like a reasonably sane approach? Anyone have another way? (Actually, I prefer using an id in loc() instead of the English text as the key -- makes templates harder to read but solves some translation issues.) -- Bill Moseley [email protected]
_______________________________________________ templates mailing list [email protected] http://mail.template-toolkit.org/mailman/listinfo/templates
