Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

catalyst::plugin::i18n(3pm) [debian man page]

Catalyst::Plugin::I18N(3pm)				User Contributed Perl Documentation			       Catalyst::Plugin::I18N(3pm)

NAME
Catalyst::Plugin::I18N - I18N for Catalyst SYNOPSIS
use Catalyst 'I18N'; print join ' ', @{ $c->languages }; $c->languages( ['de'] ); print $c->localize('Hello Catalyst'); Use a macro if you're lazy: [% MACRO l(text, args) BLOCK; c.localize(text, args); END; %] [% l('Hello Catalyst') %] [% l('Hello [_1]', 'Catalyst') %] [% l('lalala[_1]lalala[_2]', ['test', 'foo']) %] [% l('messages.hello.catalyst') %] DESCRIPTION
Supports mo/po files and Maketext classes under your application's I18N namespace. # MyApp/I18N/de.po msgid "Hello Catalyst" msgstr "Hallo Katalysator" # MyApp/I18N/i_default.po msgid "messages.hello.catalyst" msgstr "Hello Catalyst - fallback translation" # MyApp/I18N/de.pm package MyApp::I18N::de; use base 'MyApp::I18N'; our %Lexicon = ( 'Hello Catalyst' => 'Hallo Katalysator' ); 1; CONFIGURATION You can override any parameter sent to Locale::Maketext::Simple by specifying a "maketext_options" hashref to the "Plugin::I18N" config section. For example, the following configuration will override the "Decode" parameter which normally defaults to 1: __PACKAGE__->config( 'Plugin::I18N' => maketext_options => { Decode => 0 } ); All languages fallback to MyApp::I18N which is mapped onto the i-default language tag. If you use arbitrary message keys, use i_default.po to translate into English, otherwise the message key itself is returned. EXTENDED METHODS setup METHODS languages Contains languages. $c->languages(['de_DE']); print join '', @{ $c->languages }; language return selected locale in your locales list. language_tag return language tag for current locale. The most notable difference from this method in comparison to "language()" is typically that languages and regions are joined with a dash and not an underscore. $c->language(); # en_us $c->language_tag(); # en-us installed_languages Returns a hash of { langtag => "descriptive name for language" } based on language files in your application's I18N directory. The descriptive name is based on I18N::LangTags::List information. If the descriptive name is not available, will be undef. loc localize Localize text. print $c->localize( 'Welcome to Catalyst, [_1]', 'sri' ); SEE ALSO
Catalyst AUTHORS
Sebastian Riedel <sri@cpan.org> Brian Cassidy <bricas@cpan.org> Christian Hansen <chansen@cpan.org> COPYRIGHT AND LICENSE
Copyright (c) 2005 - 2009 the Catalyst::Plugin::I18N "AUTHORS" as listed above. This program is free software, you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.14.2 2010-06-14 Catalyst::Plugin::I18N(3pm)

Check Out this Related Man Page

HTML::FormHandler::TraitFor::I18N(3pm)			User Contributed Perl Documentation		    HTML::FormHandler::TraitFor::I18N(3pm)

NAME
HTML::FormHandler::TraitFor::I18N - localization VERSION
version 0.40013 language_handle, _build_language_handle Holds a Locale::Maketext (or other duck_type class with a 'maketext' method) language handle. The language handle is used to localize the error messages in the field's 'add_error' method. It's also used in various places in rendering to localize labels and button values, etc. The builder for this attribute gets the Locale::Maketext language handle from the environment variable $ENV{LANGUAGE_HANDLE}: $ENV{LANGUAGE_HANDLE} = HTML::FormHandler::I18N->get_handle('en_en'); ...or creates a default language handler using HTML::FormHandler::I18N. You can pass in an existing Locale::MakeText subclass instance or create one in a builder. In a form class: sub _build_language_handle { MyApp::I18N::abc_de->new } Passed into new or process: my $lh = MyApp::I18N::abc_de->new; my $form = MyApp::Form->new( language_handle => $lh ); If you do not set the language_handle, then Locale::Maketext and/or I18N::LangTags may guess, with unexpected results. You can use non-Locale::Maketext language handles, such as Data::Localize. There's an example of building a Data::Localize language handle in t/xt/locale_data_localize.t in the distribution. If you don't want a particular error message to go through localization, you can use 'push_errors' and 'push_form_errors' instead of 'add_error' and 'add_form_errors'. Example of getting the language handle from the Catalyst context (where the Catalyst context is passed in with 'ctx'): has '+language_handle' => ( builder => 'get_language_handle_from_ctx' ); sub get_language_handle_from_ctx { my $self = shift; return MyApp::I18N->get_handle( @{ $self->ctx->languages } ); } AUTHOR
FormHandler Contributors - see HTML::FormHandler COPYRIGHT AND LICENSE
This software is copyright (c) 2012 by Gerda Shank. This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. perl v5.14.2 2012-06-25 HTML::FormHandler::TraitFor::I18N(3pm)
Man Page