Clarification on new plone i18n system

Hola,

Can I please just get a clarification on recommended/best practice for
plone translations?

In particular, I am about to start getting a plone product (plumi.org)
translated, and we are in the process of moving from plone 2.5 to
plone 3.3 (well, plone 3.x I guess)

In particular, we are ditching the old installation method and using
the egg/buildout installation method for plumi.

So, we have:

plumi.app
plumi.content
plumi.skin

in our trunk

I am unsure as to whether it is correct to then create

plumi.*.locales
or
plumi.*.i18n

as the root folder to hold the pot/po files in our src?

cheers
L.

--

-- 
Thinks that Initech is the digital equivalent of Acme.

------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT 
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian 
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com