Skip to content
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

Translation #113

Open
4 tasks
techninja opened this issue Jul 5, 2020 · 0 comments
Open
4 tasks

Translation #113

techninja opened this issue Jul 5, 2020 · 0 comments

Comments

@techninja
Copy link
Owner

techninja commented Jul 5, 2020

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)
  • ...? There's probably a few more here
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant