How to contribute to Plone core translations¶
How to contribute to the Plone translations.
You need to have write access to https://github.com/collective/plone.app.locales to be able to commit your translation directly. You can also update a po file online and make a pull request.
If you want to test your latest translation with unreleased packages containing i18n fixes for Plone 4, get the buildout like this:
git clone -b 4.2 git://github.com/plone/buildout.coredev.git
bin/buildout -c experimental/i18n.cfg
ln -s experimental/.mr.developer.cfg
To update the buildout later:
bin/develop up -f
To update your translation, you can go there:
Here you have the following directories:
localesused for core Plone translations.
locales-addonsused for some addons packages.
locales-futureused for Plone 5 packages. The po files can change really often. The translations will normally be merged to the locales directory when Plone 5 will be released. This directory is not included in
plone.app.locales4.x releases. For developers: if you want to add a Plone 5 package to this directory, you can add it to the
experimental/i18n.cfg, don't forget to add a line in
[sources]if it's missing.
Open the po file with poedit, kbabel or any other i18n tool. For example for French:
Please do a
before editing a po file to be sure you have the latest
You can commit your translation from this locales directory:
git commit -a -m "Updated French translation"
If you do not have commit access on Github collective group. you can do the following:
Login to Github. Go to Github plone.app.locales
Press Fork. Now Github creates a copy of
package for you.
Then on your computer in
do a special git push to your own repository:
git push email@example.com:YOURUSERNAMEHERE/plone.app.locales.git
Go to Github
Press button Create Pull request. Fill it in.
The request will appear for plone.app.locales authors. If it does not get merged in timely manner, poke people on the #plone IRC channel or the mailing list below (sometimes requests go unnoticed).