-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
i18n for console messages #3384
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
Comments
It's been a while, but we, @al6862 @anpanring would like to take over this issue. Could we try it out first based on pull request #3488? |
@Bernice55231 This is pretty old and I'm not sure still relevant especially considering we have an FES system that can support translated messages as well. |
This is approved for implementation in a minor release of 2.x, but it's not quite fleshed out for assignment just yet. To move forward, this issue needs an implementation proposal as well as a volunteer to work on it. PS: This message is part of cleaning up the p5.js 2.0 roadmap prior to release, to make outstanding more more approachable for new contributors. You can join the conversation about this new version on this Discourse thread or this GitHub thread! If you're new to p5.js contribution, welcome! Please be sure to read through the contributor guidelines, and keep in mind that you should not file a pull request (or start working on code changes) without a corresponding issue or before an issue has been approved for implementation and assigned. |
Nature of issue?
In various parts of the codebase, there are console error messages for the end user hardcoded in English. We could internationalize messages to provide better support for users who speak other languages. Here are some files where I found such error messages:
This feature enhancement is not meant to cover translations themselves, but rather the architecture required to allow use of translations in the future.
The text was updated successfully, but these errors were encountered: