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
I'm not completely against adding translations to other languages. However, I've done it for other projects in the past, and for OSS projects it's trickier than it seems.
First, you need to find the right tool where people can easily contribute translations. If the process is too complex, or they need to go through a long sign-up, or there's any other blocker that can scare people, they will just not do it. Also, that tool needs to be free (or close to free) for obvious reasons.
Second, I will never know how good those translations are. By definition, people will be contributing with languages I don't know, which is always a small risk.
And third, translations get quickly outdated. While the project grows, new strings will be needed, and existing ones will change. That makes supported languages to start getting mixed with literals in the default language, which usually looks ugly and makes users loose trust in the project.
Because of that, I have usually spent my time on other stuff which adds a bigger or longer term value to the project.
No description provided.
The text was updated successfully, but these errors were encountered: