First of all, thanks for discourse. It’s really user friendly!
We’ve set up a discourse instance so people in Catalonia can discuss the principles and statutes of a newly born political party.
Language spoken in this region is very equally distributed between Catalan and Spanish, see here for a reference. It’s also a pretty sensitive issue. Most of the people can understand both languages, but feel unconfortable when they are not given a choice.
So in this context, it’s really compulsory to have a language choice. The fact that users can optionally select a language preference in their profile and that the browser language can be optionally autoselected as the site language helps a lot but doesn’t completely solve the issue: anonymous users can’t select their language.
I guess the same situation happens in other places (Quebec, for example?). In particular, in Spain it would happen in some another regions that have two official languages as well (Galicia, Valencian Community, Basque Country…), which amount to around 40% of the total population (~15million people).
I’d like a simple way of enabling a language choice in Discourse. We’ve implemented this through a new optional setting that allows admins to select a number of languages which will be displayed in the main menu allowing changing the UI language.
I’d like to ask whether there’s interest in this feature so I can open a PR to the discourse repository.
Yes, we have it enabled as well, but that setting is not 100% accurate (say, catalan speaking user connecting from her work’s brower which is set to Spanish). We want to always let the user override the language they are “given”.
To be honest, I had the same feedback from our clients. Although the reason to put it there was just to simplify the implementation, after a second thought it does not seem like a bad place to me. This is a very unusual action (not a lot of users will actually need it, and in any case, it will be used at most once by most users). So it feels bad that it takes a permanent space of the screen. As per the difficulty of finding it… well, if I proactively look for the option, I think the hamburger is the first place I would try.
I just tried my initial implementation locally and it works. So I assumed it would work in our beta/productions environments as well… my bad … Is the fact that it works locally something that you would expect, @sam?