FOLIO front-end code uses translation keys to fetch actual text in English or any other language.
...
One option is to take the latest translations from https://folio-testingsnapshot.dev.folio.org/, another option is to take the translation files from https://github.com/gbv/folio-translations.
Manual
Do to it manually use the browser developer tools to find out the current number folio-testing uses, for example Option 1: Take the file from https://github.com/gbv/folio-testing.dev.folio.org/translations/de-1605513539114translations platform-complete directory, for example de.json. If you your own installation has de-1601343197440.json merge them:jq -s '.[0] * .[1]' de-1601343197440.json de-1605513539114.json > de-1601343197440.json.new
Then use the joined file: mv de-1601343197440.json.new de-1601343197440.json
Automated
To do it automatically use this script:
...
| language | bash |
|---|---|
| title | translations-upgrade |
...
Option 2: Use the browser developer tools to find out the current number folio-snapshot uses, for example https://folio-
...
snapshot.dev.folio.org/
...
translations
...
/
...
de-1605513539114.json
...
. Download it. If your own installation has de-1601343197440.json merge them:jq -s '.[0]
...
*
...
.[1]'
...
de-1601343197440.json de-1605513539114.json
...
>
...
de-1601343197440.json.new
...
Then use the joined file: mv de-1601343197440.json.new
...
de-1601343197440.json
Automated
https://github.com/gbv/folio-translations
Clean backport using yarn build
The backport method described above is a hack.
The clean way to use more recent translations is to replace them during the front-end build process.
After runningyarn install but before running yarn build copy the new translations into the node_modules/@folio/${application}/translations/ui-${application}/${locale}.json files.
We don't know of anyone that uses this method, no script is available for this yet.