-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add instructions for changing translated strings #6528
Add instructions for changing translated strings #6528
Conversation
Add instructions to the developer documentation for proper housekeeping of the translations when editing strings.
We have |
As per code review feedback, we should use the npm run scripts i18n and i18n-prune instead of editing the i18n JSON files directly.
Replace an inline, parenthetical note about possible failures of the `npm run` scripts with additional items in the Requirements section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The reason for this change is that now two sections in the document reference the npm i18n
script.
Ah, it doesn't have a hyphen so actually it's Also, do you think it makes more sense to add the bit about editing after 'adding new strings'? Most of the time people will be adding strings I suspect, rather than editing existing ones. |
The `npm run` command `i18n-prune` is actually `prunei18n`.
Move "Editing existing strings" to after "Adding new strings".
I don't have a strong preference on the ordering. I have so far found myself editing more strings than adding new strings, |
Add instructions to the developer documentation for proper housekeeping of the
translations when editing strings.
Signed-off-by: Aidan Gauland aidalgol+ghpr@fastmail.net