Call for translators for Plone 6

Development Translations and i18n/l10
1

Everyone is working hard on getting Plone 6 ready and we think that it is time to think also on translating Plone 6 interfaces!

Most of the Plone Classic is already translated. Not many things have changed since Plone 5.2 so the translation status of version 6 is more or less the same as in 5.2. So far so good.

But we need an effort to get Volto translations. Right now we only have translations for 9 languages and only 3 of them are above the 90% translated (ca, de and pt-br).

We have several nightly-run Jenkins jobs to check the translation status:

This post is then to do a heads up and encourage translators to translate Plone 6's UIs (classic and Volto) into their language.

Some weeks ago we started a thread here to know whether the community wants to move to a web based translation tool. Due to the lack of response (we only had 6 votes), we have decided to let the translation process as it is and to keep working on PO files on github.

The translation process is as follows:

Volto

  1. Go to https://github.com/plone/volto and clone it into your computer
  2. Create a new branch to prepare the translations
    3.a Translate your language po file found at locales/{language_code}/LC_MESSAGES/volto.po
    3.b Alternatively, if your language file does not exist, create a new folder at locales/{language_code}/LC_MESSAGES/, copy over the volto.pot file there as volto.po and start translating.
  3. Commit your changes and add a Pull-Request.

We will review it and include it in the next Volto release!

Classic UI

  1. Go to https://github.com/collective/plone.app.locales and clone it into your computer
  2. Create a new branch to work on your translations
  3. Translate the PO files under your language of choice at plone/app/locales/locales/{language_code}/LC_MESSAGES/*.po. In Classic UI we have several language files because some of the original messages are spread over several language domains and products.
  4. Commit your changes and add a Pull Request with them. Try to have a review from a colleague, specially in case you are translating a file with already some translations. This is just to have coherent translations all over Plone.
1 Like
2

Hi! I added recently some changes, are they ok? Thanks!

3

I see your commits there, so yes, they will be published in the next alpha release!

4

We'll add an update soon for Romanian.

1 Like
5

Romanian traslations: Romanian transations by sboghy · Pull Request #3227 · plone/volto · GitHub

2 Likes
6

I did a bit of translation of Classic to Norwegian (no).

  1. Should I commit the chances, or wait until I have translated 'most' (could take some time)

  2. I usually use PO-edit (Mac), can anyone recommend something that can spell-check my po-files

7

Should I commit the chances, or wait until I have translated 'most' (could take some time)

Whatever you prefer. We release a new version of plone.app.locales when a new version of Plone is due.

I usually use PO-edit (Mac), can anyone recommend something that can spell-check my po-files

I also use Poedit on Linux to edit the translation files and I would say that it does spellchecking. At least all unknown words are underlined in red.

I alos like Poedit because of the translation memory. This way I can easily translate po files reusing existing translations.

8

Hmm, mine does not, maybe I have an old version, or the program gets mixed up with the two versions of Norwegian we have ( but it did not mark a word that does not exist in any of them)

UPDATE: Updating to last version of PoEdit works/ spell-checks. I also had to change language to (the correct) no (no_nb), since it was set to 'nn' (we have two 'languages' in Norway). The nn dictonary needs to be downloaded (from OpenOffice) and installed (in PoEdit)