I’d like to start a discussion about supporting localizations in Discourse. Currently Discourse has a few (almost) complete contributed translations. However, the current codebase does not support switching to another locale and has a few places that are hard-coded to use the “en” locale.
Server-side (Ruby code) is fine, and setting
But it’s not clear to me how to support proper i18n to the JS side of Discourse with respect to Rails’ asset pipeline. I would really like to help with implementing this, but I am mostly a Rails noob, and it seems to me that there is no easy solution. Having a config-dependent asset brings a lot of trouble. Exporting all the locales in a JS file currently generates a filesize of a few hundred kB, but can easily get into many megabytes when we have a lot of localizations.