Description
How to contribute to the Plone translations.
First you need commit access to collective repository if you want to commit your translation.
If you want to test your latest translation with unreleased packages containing i18n fixes for Plone 4, get the buildout like this:
svn co https://svn.plone.org/svn/plone/buildouts/plone-coredev/branches/4.0 plone4
cd plone4
python2.6 bootstrap.py
bin/buildout -c experimental/i18n.cfg
bin/instance fg
To update the buildout later:
svn up
rm .mr.developer.cfg
ln -s experimental/.mr.developer.cfg
bin/develop up -f
To update your translation, you can go there:
cd src/plone.app.locales/plone/app/locales/
Here you have the following directories:
If you do svn info in the locales directory, you'll see it is actually a svn external reference to: https://svn.plone.org/svn/collective/PloneTranslations/trunk/locales
Open the po file with poedit, kbabel or any other i18n tool. For example for French:
poedit locales/fr/LC_MESSAGES/plone.po
You can commit your translation from this locales directory:
svn ci -m "Updated French translation"
Download the buildout:
svn co https://svn.plone.org/svn/plone/buildouts/plone-coredev/branches/3.3 plone3
cd plone3
python2.4 bootstrap.py
bin/buildout -c i18n.cfg
bin/instance fg
To update the buildout later:
svn up
bin/develop up -f
To update your translation, you can go to src/plone.app.locales/plone/app/locales/i18n and src/plone.app.locales/plone/app/locales/locales.
If you do svn info in the i18n directory, you'll see it is actually an svn external reference to: https://svn.plone.org/svn/collective/PloneTranslations/branches/3.x/i18n
Please ask questions on the plone-i18n mailing-list.
The source code of this file is hosted on GitHub. Everyone can update and fix errors in this document with few clicks - no downloads needed.
For basic information about updating this manual and Sphinx format please see Writing and updating the manual guide.