You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: contributor_docs/internationalization.md
+6-1Lines changed: 6 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -82,7 +82,12 @@ The easiest way to do this is to add your language code (like "de" for German, "
82
82
83
83
This will generate you a fresh translations file in`translations/{LANGUAGE_CODE}/`! Now you can begin populating it with your fresh translations! 🥖
84
84
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.
0 commit comments