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 internationalization support to Web UI #70
Comments
As long as all the UI strings are in the templates then it is just a matter of using the Jinja2 template i18n support: Wrap translatable statements in {% trans %} tags: Then install the translation into the Jinja2 environment: And I imagine this would have to be linked to a working settings page. |
We can detect the language by looking at the "Accept-Language" HTTP header sent by the browser. This should also be able to be overridden by a cookie set by the settings page. |
Yoshio, are we ready to get our first POT file translated? If so, can you e-mail a POT file to me and I'll forward it to the OLPC contact who wants to do the translation? Thanks for your work on this. |
On Tue, Jul 23, 2013 at 11:44:36AM -0700, Braddock Gaskill wrote:
No, I have to re-do the license translation part on settings.html. |
OLPC School Server project wants French and Creole versions of the web ui for Haiti deployment. They have offered to do all the translation work necessary, but we would need to add i18n support to our web UI. Any takers?
The text was updated successfully, but these errors were encountered: