Skip to content

Commit 703ada6

Browse files
erralstevepiercy
authored andcommitted
resync Volto translation!
1 parent 6b63df0 commit 703ada6

File tree

1 file changed

+20
-2
lines changed

1 file changed

+20
-2
lines changed

docs/i18n-l10n/resync-translations.md

Lines changed: 20 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,9 @@ html_meta:
88

99
(resync-translations-label)=
1010

11-
## Resync translations
11+
## Resync translations in Plone back-end
1212

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

1515
Usually Translations team handles the update of those po files so you don't need to worry about it. Here we will explain the procedure to update such files.
1616

@@ -84,3 +84,21 @@ fullrelease
8484
6. Check that the release is published on pypi: https://pypi.org/project/plone.app.locales/
8585

8686
7. Inform the release manager about the new version
87+
88+
## Resync of translations in Volto
89+
90+
In Volto, the GitHub test setup warns a developer when her new bits require regenerating the translation file. This is done running a yarn script as follows:
91+
92+
```bash
93+
yarn i18n
94+
```
95+
96+
This will update the po files and will leave them ready to be translated by translators.
97+
98+
## Create a new release of Volto with the new translations
99+
100+
The Volto release process requires running the same yarn script as in the previous step to convert the translations in po files to the JSON files that Volto uses to render the user interface.
101+
102+
```bash
103+
yarn i18n
104+
```

0 commit comments

Comments
 (0)