Resync translations

Resync translations#

This chapter discussions how to resynchronize translations in both the backend and frontend, and how to make releases for each.

Resync translations in the Plone backend#

Plone PO files need to be updated each time a new string is added into the Plone interface or each time one of those strings is updated. Those translations are not only used in Plone Classic UI, but many of them are also exposed through the REST API to Volto.

Usually the Plone Translations Team updates these PO files. Here we will explain the procedure to update them.

Clone the relevant branch of buildout.coredev corresponding to the Plone version you want to update.
Initialize the buildout.
```
./bootstrap.sh
```
Run buildout using the experimental/i18n.cfg file:
```
./bin/buildout -c experimental/i18n.cfg
```
Run the i18n-update-all script:
```
./bin/i18n-update-all
```
The script will go through Plone source code and will update all pot and po files in the plone.app.locales package.

Commit the changes and push back to GitHub:

cd src/plone.app.locales
git add plone
git commit -m "Update translation files"
git push origin

Create a new `plone.app.locales` release#

Translators will take care of translating po files into their languages. When the release manager requests to create a new plone.app.locales release, the procedure is the following:

Create a virtualenv with zest.releaser and zest.pocompile installed:

`which python3.10` -m venv .
./bin/pip install zest.releaser zest.pocompile
source bin/activate

Go to the plone.app.locales directory and pull the changes:
```
cd src/plone.app.locales
git pull
```
Verify there is a changelog entry for each change, adding any missing entries if necessary.
Verify there are no errors in the PO files:
```
    for po in `find . -name "*.po"` ; do msgfmt --no-hash -o `dirname $po`/`basename $po .po`.mo $po; done
```
You can ignore the errors 'msgid' and 'msgstr' entries do not both end with '\n'. If there are other errors, please fix them.
Release.
```
fullrelease
```
Check that the release is published on PyPI at https://pypi.org/project/plone.app.locales/.
Inform the release manager about the new version.