Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

There are several issues to solve:

  • make dynamic language selection work well for the UI translation (it kind of works, but there are edge cases where parts of the UI are in one language and other parts in another - I think the issues are in how translations work in the jinja2 templates).
  • make selection of content depend on the current language
  • possibly add language code to the url scheme - there is a an app called localeurl, maybe that can help.
  • add UI for translation of the content

Consider that there may be another solution - mount language specific sites on the subdomains (wikipedia does it this way). This method would allow locating the servers for specific languages physically in the regions where there are more speakers of that language, but with this approach it would be harder to synchronize user accounts and the user sing-in.