PrivateCoffee/element-web
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 3

Correct instructions to use the i18n scripts

Browse source 
As per code review feedback, we should use the npm run scripts i18n and
i18n-prune instead of editing the i18n JSON files directly.
This commit is contained in:
Aidan Gauland 2018-04-21 21:36:41 +12:00
parent 69bb020e5c
commit 6d74d5f8b7
1 changed files with 3 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
docs/translating-dev.md
View file

@ -28,8 +28,9 @@ function getColorName(hex) {
## Editing existing strings ## Editing existing strings
1. Edit every occurrence of the string in `src/i18n/strings/en_EN.json` and inside `_t()` and `_td()` in the JSX files. 1. Edit every occurrence of the string inside `_t()` and `_td()` in the JSX files.
1. Remove every translation of this string from `src/i18n/strings/*.json`, _except_ for `src/i18n/strings/en_EN.json`, as that string no longer exists. 1. Run `npm run i18n` to update `src/i18n/strings/en_EN.json`. (Be sure to run this in the same project as the JSX files you just edited.)
1. Run `npm run i18n-prune` to remove the old string from `src/i18n/strings/*.json`.
## Adding new strings ## Adding new strings