Re: HTML::Template I18N/L10N/gettext

Basically, you create a master template, where you designate whats part of your dictionary/catalog

Then use poedit to add translations/catalogs

You could generate a specific template for each language but that probably doesn't play well with catalog tools

You should have the translator proofread the stuff in context ie final form

Comment on Re: HTML::Template I18N/L10N/gettext

Replies are listed 'Best First'.
Re^2: HTML::Template I18N/L10N/gettext by skazat (Chaplain) on Sep 19, 2015 at 00:04 UTC
HTML::Template::Compiled::Plugin::I18N doesn't look straightforward at all, and would require me to use a different templating language (with yes, the same syntax, but I'm sure to run into problems). Template::Plugin::Filter::I18N is a broken link. Is it this?. If so, there's no documentation. Catalog tools? Do you mean for indexing (search, etc?) -skazat	[reply]
Re^3: HTML::Template I18N/L10N/gettext by Anonymous Monk on Sep 19, 2015 at 00:52 UTC
HTML::Template::Compiled::Plugin::I18N doesn't look straightforward at all, and would require me to use a different templating language (with yes, the same syntax, but I'm sure to run into problems). Right, link is to give perspective Template::Plugin::Filter::I18N is a broken link. Is it this?. If so, there's no documentation. Well, thats a metacpan bug it seems. Template::Plugin::Filter::I18N works and yes the docs are succinct :) I for got to give Catalyst::Plugin::I18N::Manual its more detailed much wider perspective, it links gettext/catalog tools like poedit	[reply]
Re^4: HTML::Template I18N/L10N/gettext by skazat (Chaplain) on Sep 19, 2015 at 00:55 UTC
I appreciate all the resources, they are some of the ones I've been looking at, myself. Looks as if this is a very TIMTOWTDI part of Perl development! I'm actually surprised there aren't more mature workflows. -skazat	[reply]