1
0
Fork 0

Use update i18n command instead of generate

This commit is contained in:
Chocobozzz 2020-08-24 09:35:27 +02:00
parent 1e7eb457ed
commit 49a56c7203
No known key found for this signature in database
GPG key ID: 583A612D890159BE
3 changed files with 4 additions and 4 deletions

View file

@ -35,7 +35,7 @@
"danger:clean:dev": "scripty",
"danger:clean:prod": "scripty",
"danger:clean:modules": "scripty",
"i18n:generate": "scripty",
"i18n:update": "scripty",
"plugin:install": "node ./dist/scripts/plugin/install.js",
"plugin:uninstall": "node ./dist/scripts/plugin/uninstall.js",
"i18n:create-custom-files": "node ./dist/scripts/i18n/create-custom-files.js",

View file

@ -2,6 +2,8 @@
set -eu
git fetch weblate && git merge weblate/develop
npm run build -- --i18n
cd client

View file

@ -8,10 +8,8 @@ Source files are in `client/src/locale` and translated files merged from [Weblat
Will generate XLIFF base files for Angular (`angular.xlf`) and JSON files for the player (`player.en-US.json`) and the server (`server.en-US.json`).
Then, it will merge new translation keys into localized Angular files (`angular.fr-FR.xlf` etc).
**Only generate new translations after a Weblate pull to avoid conflicts**
```
$ npm run i18n:generate
$ npm run i18n:update
```