Clarification on new plone i18n system

[datakid]

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 
_______________________________________________
Plone-i18n mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-i18n

[Hanno Schlichting-3]

Martin Stadler wrote:
> Am 01.06.2009 um 04:48 schrieb Lachlan Musicman:
>> 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?

If the three packages are independently usable and need localization
files, I'd put the pot/po files into the packages themselves. If the
three packages only work in combination, you could also add an extra
plumi.locales package that holds the translation files for all three
packages.

> This is a very good resource:
>      http://maurits.vanrees.org/weblog/archive/2007/09/i18n-locales-and-plone-3.0
>
> In addition, I think since Plone 3.1 or so you can also put an extra  
> i18n folder in your package and Plone will use it for the old "Plone"  
> namespace so no old-style product is required for translations.

Nope. Since Plone 3.3 (currently in release candidate stage) you can
extend translation domains defined in locales folders in a different
package. Before there could only ever be one package holding
translations per domain in locales folders.

In order to extend translations you do need to use the approach the
other files in that domain use. So for the various "Plone" domains you
need to stick to the i18n folders.

Hanno


------------------------------------------------------------------------------
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 
_______________________________________________
Plone-i18n mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-i18n

[Hanno Schlichting-3]

Martin Stadler wrote:

> Am 01.06.2009 um 12:10 schrieb Hanno Schlichting:
>
>>> In addition, I think since Plone 3.1 or so you can also put an extra
>>> i18n folder in your package and Plone will use it for the old "Plone"
>>> namespace so no old-style product is required for translations.
>> Nope. Since Plone 3.3 (currently in release candidate stage) you can
>> extend translation domains defined in locales folders in a different
>> package. Before there could only ever be one package holding
>> translations per domain in locales folders.
>>
>> In order to extend translations you do need to use the approach the
>> other files in that domain use. So for the various "Plone" domains you
>> need to stick to the i18n folders.
>>
>> Hanno
>
> Sorry. What did I say? I meant domain, not namespace. Maybe that's it?

Ah, now I see what you meant. Yes, indeed since Plone 3.1 you don't need
to have a "Products.*" product anymore to be able to use i18n folders at
all. Since that release you can use i18n folders inside packages.

What I meant is that you still need to use an i18n folder to extend the
Plone domain files and cannot put those into a locales folder.

Hanno


------------------------------------------------------------------------------
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 
_______________________________________________
Plone-i18n mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-i18n