Skip to content

Commit 6d74d5f

Browse files
committed
Correct instructions to use the i18n scripts
As per code review feedback, we should use the npm run scripts i18n and i18n-prune instead of editing the i18n JSON files directly.
1 parent 69bb020 commit 6d74d5f

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

docs/translating-dev.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,8 +28,9 @@ function getColorName(hex) {
2828

2929
## Editing existing strings
3030

31-
1. Edit every occurrence of the string in `src/i18n/strings/en_EN.json` and inside `_t()` and `_td()` in the JSX files.
32-
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.
31+
1. Edit every occurrence of the string inside `_t()` and `_td()` in the JSX files.
32+
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.)
33+
1. Run `npm run i18n-prune` to remove the old string from `src/i18n/strings/*.json`.
3334

3435
## Adding new strings
3536

0 commit comments

Comments
 (0)