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
Pedal would be entirely capable of handling translations to other languages - error messages could come out in whatever native language we provide translations for. I'm sure there's some real headaches here for presenting the information in different languages, and there may be some learning implications for folks who aren't then ready to move to english, but I'm betting that the benefits outweigh the costs for many folks?
Probably the big thing is to explore gettext, make sure there isn't anything better, and then just go through our codebase and add _("") around all the strings. I suspect that it would actually be a lot more trivial to do all the setup and would help us get better about First Class Feedback everywhere.
Of course, from there, we'd need folks to help write the language bindings. Doing a Spanish version might be a fun start, though of course someone would need to come along and fix my horribleness. And do we even have any audience interested in this?
What would this require for the Skulpt version? I wonder if it would actually have a significant file size improvement, since we'd stop embedding large strips in the source code?
The text was updated successfully, but these errors were encountered:
How often do I forget what I've written before? #34 discusses exactly this. I increasingly think this is worth investing in. It'll be a bit of a pain, but if we're really aiming for a broader market then it will be totally worth it.
Pedal would be entirely capable of handling translations to other languages - error messages could come out in whatever native language we provide translations for. I'm sure there's some real headaches here for presenting the information in different languages, and there may be some learning implications for folks who aren't then ready to move to english, but I'm betting that the benefits outweigh the costs for many folks?
Probably the big thing is to explore
gettext
, make sure there isn't anything better, and then just go through our codebase and add_("")
around all the strings. I suspect that it would actually be a lot more trivial to do all the setup and would help us get better about First Class Feedback everywhere.Of course, from there, we'd need folks to help write the language bindings. Doing a Spanish version might be a fun start, though of course someone would need to come along and fix my horribleness. And do we even have any audience interested in this?
What would this require for the Skulpt version? I wonder if it would actually have a significant file size improvement, since we'd stop embedding large strips in the source code?
The text was updated successfully, but these errors were encountered: