Currently, communities using the content localization feature can select multiple languages to show localized content. For example, a forum may have German, English, French set up in content localization supported locales.
Right now, users are only able to select one of the languages the forum supports.
If a topic has posts written in all three languages, Günter would see all those in German only despite being fluent in all three languages.
The goal of this feature topic is to allow such multilingual users to select multiple languages and see the posts written in their original word, instead of just one language. Another thing to be mindful of is that user.locale is currently being used to determine the language controls (buttons, labels, tooltips, etc), and that should be the user's primary language.
Here are supporting quotes from largely the same few topics:
Multilingual user feedback on Automatic TranslationsContent Localization and Automatic Translations for Your CommunityIf I'm fluent in German, English and French, I would like to see the original, untranslated content if it is in any of those three languages.
Everything is translated, help!I talk differently to Germans. Differently to Polish. Differently to Swiss. Differently to Icelandic. Differently to French. Differently to Slovak. And now maybe differently to Finish. I know their languages and cultures enough to be careful.
Everything is translated, help!And as you mention, it would really be nice to have not a single, but multiple languages which are not translated.
Content Localization and Automatic Translations for Your CommunityAs an example, YouTube now allows you to define one single language you are supposed to understand, and auto-translates everything to that language, so I have to choose if I want my french video titles badly translated to english, or my english video titles badly translated to french.
create user pref to let them decide which languages they always want to read in the original
One UX question we'll have to figure out is how to surface the option to the user. If we use the existing user.locale and allow an array e.g. ['en', 'ja', 'ko'], there are many other places that would be affected, as opposed to keeping user.locale to one and adding another user field altogether. If we add a new user field, we also have to think about location.
Discuss this on our forum.