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
add i18n support #1130
Comments
I agree. PRs welcome! |
Want i18n on the web interface (not content of pages) as well. Is anybody already working on this? |
Not that I know of. |
@jokester Care to contribute a PR? |
bartkamphorst: guess I can do something on i18n of Web UI. Do we have a todo list on this topic? |
Great! No, there's no todo list as of yet. @dometto Any thoughts about this? One note, when you start work on this, make sure to branch from the |
No experience with this. @jokester, maybe you can give an indication of how'd you go about this and we can comment on any issues we (hopefully) foresee? |
I made a small list after looking at
|
@jokester, sorry for the late reply. We would be very happy with this, if you're still able and willing to work on it. The main pointer I can give you now is to open your PR against the |
@jokester I know it's been a while, but would you still be willing to work on |
Ping @jokester . |
Implemented by @benjaminwil in #1679! 🥇 |
I plan to i18n all of the English hard-coded strings in the next couple of weeks. |
Gollum is not support i18n. I think should add this funtion.
The text was updated successfully, but these errors were encountered: