Skip to content

Commit d3813a3

Browse files
committed
Update i18n contributor_docs
1 parent 41508b1 commit d3813a3

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

contributor_docs/internationalization.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,12 @@ The easiest way to do this is to add your language code (like "de" for German, "
8282

8383
This will generate you a fresh translations file in `translations/{LANGUAGE_CODE}/`! Now you can begin populating it with your fresh translations! 🥖
8484

85-
You'll also need to add an entry for it in `translations/index.js`. You can follow the pattern used in that file for `en` and `es`.
85+
You'll also need to add an entry for it in [`translations/index.js`](../translations/index.js) and [`translations/dev.js`](../translations/dev.js). You can follow the pattern used in that file for `en` and `es`.
86+
87+
### Testing changes
88+
The bulk of translations are not included in the final library, but are hosted online and are automatically downloaded by p5.js when it needs them. Updates to these only happen whenever a new version of p5.js is released.
89+
90+
However, if you want to see your changes (or any other changes which aren't released yet), you can simply run `npm run dev` which will build p5.js configured to use the translation files present locally on your computer, instead of the ones on the internet.
8691

8792
### Further Reading
8893

0 commit comments

Comments
 (0)