5

I'm developing a CakePHP plugin which should support multiple languages. The procedure for i18n localisation is documented here, but plugins aren't explicitly covered. Is this structure below supposed to work? Because it isn't for me at the moment, but I might be overlooking something.

/myapp/
  /plugins/
    /myplugin/
      /locale/
        default.pot
        /nld/
          /LC_MESSAGES/
            default.mo
            default.po

And calling the translation in the plugin controller like so:

Configure::write('Config.language', 'nld');

In my plugin views the localisation function is formatted like this:

__('MyPluginName', 'MyDefaultString')

Some of the posts on CakePHP and the localisation of plugins mention that all locales should go in to /myapp/locale/, instead of the plugin directory, but wouldn't that defy the purpose of the modular plugin structure? The entries I've read are from 2008 (this one for example), so I hope this isn't the case anymore.

Could anybody provide me with some more details on localising a Cake plugin, perhaps even a small step by step tutorial?

mensch
  • 4,411
  • 3
  • 28
  • 49

1 Answers1

1

Take a look at Plugin development tips and tricks article:

Localization for plugins is handled well and you can use it simply by giving a plugin name for your po or mo files.

bancer
  • 7,475
  • 7
  • 39
  • 58
  • Thanks! I followed the direction in that article and it still didn't work. Turns out I used the wrong language code, it should be "dut" instead of "nld". That's the one thing I didn't consider. – mensch Jun 14 '11 at 15:29
  • 1
    It may have not worked in the past as referenced here: Ticket references : http://code.google.com/p/lilblogs/source/browse/wiki/LocalizeHowTo.wiki?r=31 https://groups.google.com/forum/#!topic/croogo/Dn8zqBu_1QU[1-25] – snowflake Aug 14 '12 at 16:14