How to contribute to Plone core translations

Description

How to contribute to the Plone translations.

Introduction

First you need commit access to collective repository if you want to commit your translation.

Updating translations for Plone 4.0/4.1

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:

  • i18n/kupu used only for Products.kupu. This directory is not included in plone.app.locales, it's included in Products.kupu. It's only kept here for convenience.
  • locales used for core Plone translations.
  • locales-addons used for some addons packages.
  • locales-future used for Plone 5 packages. The po files can change really often. The translations will normally be merge to the locales directory when Plone 5 will be released. This directory is not included in plone.app.locales 4.x releases. For developers: if you want to add a Plone 5 package to this directory, you can add it to the plone5 variable in experimental/i18n.cfg, don't forget to add a line in [sources] if it's missing.

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"

Updating translations for Plone 3.3

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

Support

Please ask questions on the plone-i18n mailing-list.




Edit this document

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.

  1. Go to How to contribute to Plone core translations on GitHub.
  2. Press Fork and edit this file button.
  3. Edit file contents using GitHub's text editor in your web browserm
  4. Fill in the Commit message text box at the end of the page telling why you did the changes. Press Propose file change button next to it when done.
  5. On Send a pull request page you don't need to fill in text anymore. Just press Send pull request button.
  6. Your changes are now queued for review under project's Pull requests tab on Github.

For basic information about updating this manual and Sphinx format please see Writing and updating the manual guide.