i18n: Expose translator language switching feature for integration

[almchung]

How would this new feature help increase access to p5.js?

This proposes to extend our existing internationalization tool and exposes its features for future integration tasks (e.g. as discussed in p5.js web editor's issue #1943 with @outofambit ).

Most appropriate sub-area of p5.js?

• [ ] Accessibility (Web Accessibility)
• [ ] Build tools and processes
• [ ] Color
• [ ] Core/Environment/Rendering
• [ ] Data
• [ ] DOM
• [ ] Events
• [X] Friendly error system
• [ ] Image
• [ ] IO (Input/Output)
• [X] Localization
• [ ] Math
• [ ] Unit Testing
• [ ] Typography
• [ ] Utilities
• [ ] WebGL
• [ ] Other (specify if possible)

Feature enhancement details:

1. Expose the language switching function This mainly means to extend setTranslatorLanguage() from our i18n module [LINK]. p5._setTranslatorLanguage() can be a way to do this [LINK].
2. Expose a function listing available translator language We will add p5._availableTranslatorLanguages() to query for the settings page to know which translations are supported in the sketch's version of p5.

Checklist:

• [ ] Add p5._setTranslatorLanguage()
• [ ] Add p5._availableTranslatorLanguages()

[almchung]

This will be on hold until early this summer when the development direction for the FES becomes clearer. Thank you!

[Ashley-Y-Lin]

Do we have a better sense of the development direction for FES? I'd be excited to try implementing some of the features above if so.

[almchung]

Hi @Ashley-Y-Lin, thank you for your interest! We got several open issues for FES, including this one. We may work on major ones like decoupling FES (#5629) during the summer, so you may want to wait to work on this particular issue until late summer. But meanwhile, please feel free to jump in and work on other open issues.