On Wed, Oct 31, 2007 at 05:04:28PM -0400, Dominic Germain wrote:
> We have a running setup with Perl module in ISO-8859-1 (latin1) and
> templates in UTF-8.
> In TT's view : ENCODING => 'ISO-8859-1'
You are telling Template Toolkit that your templates are Latin1, but
you say your temp
On Wednesday 31 October 2007 23:10:25 Brian Cassidy wrote:
> Mario Minati wrote:
> > All the strings without [_1] are being translated as expected.
>
> Although you didn't actually say what you're getting as output, I
> suspect you'll want to use %1 format instead of [_1] in the .po file.
Thanks B
On Wed, Oct 31, 2007 at 07:10:25PM -0300, Brian Cassidy wrote:
> Mario Minati wrote:
> >All the strings without [_1] are being translated as expected.
>
> Although you didn't actually say what you're getting as output, I
> suspect you'll want to use %1 format instead of [_1] in the .po file.
Loo
Mario Minati wrote:
All the strings without [_1] are being translated as expected.
Although you didn't actually say what you're getting as output, I
suspect you'll want to use %1 format instead of [_1] in the .po file.
-Brian
___
List: Catalyst@li
Hi,
We are currently building an application using Catalyst framework and
have a lot of encoding problem. Since we use a lot on french
characters (like é-è-ê-à-ç), we need to take care of the encoding of
Perl module and TT templates.
We have a running setup with Perl module in ISO-8859-1
Hi,
I'm useing
$c->stash->{page}
= $c->loc( "New branch for [_1]", $company->name );
to internationalize my catalyst app.
In my I18N/de.po I have:
msgid "New branch for [_1]"
msgstr "Neue Niederlassung für [_1]"
All the strings without [_1] are being translated as expected.
I'm ver
Christian Storm wrote:
> Any plans for Bay Area training sessions?
Not currently, but I will put you on a list of potentially interested
parties. If anyone else is interested, mail me off-list with your
location. If it turns out that there are enough people interested in a
class somewhere, I do
Oleg Pronin wrote:
> I put these things into MyApp::SAME_AS_CATALYST_BASE_CLASSES, i.e:
> MyApp::Catalyst::Controller
> MyApp::Catalyst::View::TT
> etc.
> It's clean and nice :)
I do the same thing. It works out great if you have a lot og MyApp::
modules that have nothing to do with Catalyst, like
I put these things into MyApp::SAME_AS_CATALYST_BASE_CLASSES, i.e:
MyApp::Catalyst::Controller
MyApp::Catalyst::View::TT
etc.
It's clean and nice :)
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
