-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
Internationalization support #182
Comments
Does this assume/mean that there's already contributors for different languages? I don't mind doing some of the |
The original idea was simply to make use of gettext, but we'll have problems if we blindly do that, so what you're suggesting I think is a requirement really, and right now we have no such contributors dedicated that, so I consider this back burner for the moment. But of course, anyone can pick it up. |
👍 if you ever move in this front lemme know or simply update this issue. I'll be willing to make portuguese the first alternative language. 😄 |
Count me in too! I can help with Galician and Spanish :) |
Galician ❤️ |
As a global community we have to recognize that a lot of members of our community do not speak or read English as a first language or at all. In order to support our members around the world and provide meaningful content to said members we must support internationalization. This can be achieved using gettext.
The app needs to try and detect the locale of the request and redirect based on said locale. For example if the user's locale is Japanese then the user should be redirected to
/jp/
.We should also provide a way for users to to choose a locale from a drop down member and/or be able to set their preferred locale which would be persisted in cookies and/or the database.
The text was updated successfully, but these errors were encountered: