Yup, it's a 'real' plugin USEd in MyApp.pm and called Catalyst::Plugin::PluginName placed in MyApp/lib/Catalyst/Plugin/PluginName.pm.
And the weird thing is I swear it wasn't working yesterday but today it is using the call you've mentioned. And I'm sure I didn't change anything connected with l10n. Thanks anyway for a fast reply ;) -- Jan Grmela jan.grm...@imakers.cz +420 608 110 686 iMakers, s.r.o. Absolonova 725/81, Brno, 62400, Czech Republic ICO/Id: 29228875 DIC/VAT No: CZ29228875 On Sep 3, 2012, at 21:43 , Tomas Doran wrote: > > On 3 Sep 2012, at 08:53, Jan Grmela wrote: >> What is the best way to localize strings in a Catalyst plugin? > > If it's a 'real' plugin, then it's already composed onto the app, and so you > can just use $c->loc - do you instead mean a model or other component that > doesn't have such easy access? > > Cheers > t0m > > > _______________________________________________ > List: Catalyst@lists.scsys.co.uk > Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst > Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ > Dev site: http://dev.catalyst.perl.org/ _______________________________________________ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
