From RoboPaint, I've pulled a LOT of the existing translation strings, unfortunately the context for settings, and the exact wording no longer matches up quite a bit. The good news is I've installed i18next successfully and it installs as Express middleware, allowing for a t() func to be passed upon requests, so even stored requests with translation strings can be converted into their target language using the initial request headers.
This does not apply to embedded UI, but should work for all translatable messages coming from the API by default. Colorsets had nearly 100% coverage in RoboPaint so this has been done first, but we still need:
[ ] Error return strings for all endpoints
[ ] Static UI elements (take from any reasonably matching RoboPaint UI)
[ ] Progress strings (server based translation, assuming we can know from sockets what the user wants)
From RoboPaint, I've pulled a LOT of the existing translation strings, unfortunately the context for settings, and the exact wording no longer matches up quite a bit. The good news is I've installed
i18nextsuccessfully and it installs as Express middleware, allowing for at()func to be passed upon requests, so even stored requests with translation strings can be converted into their target language using the initial request headers.This does not apply to embedded UI, but should work for all translatable messages coming from the API by default. Colorsets had nearly 100% coverage in RoboPaint so this has been done first, but we still need: